- dovecot - dovecot.org

[Dovecot] Issues with VANISHED CHANGEDSINCE
by Michael J Rubinsky 09 Jun '14

09 Jun '14

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was only one or two emails that were removed since the provided MODSEQ value. C: 8 UID FETCH 1:* UID (VANISHED CHANGEDSINCE 587742) S: * VANISHED (EARLIER) 1:119944,119947:123482,123484:128043,128045:130388,130390:130456,130458:132127,132129:135832,135834:136201,136203:136301,136303:136316,136318:138502,138504:140099,140101:141908,141910:142607,142609:142744,142746:142865,142867:143160,143164:143173,143176:143179,143181:143187,143189:143190,143192:143195,143197:143270,143272:143273,143275:143280,143282:143302,143305:143307,143309:143318,143320:143333,143335:143337,143339:143341,143343:143375,143377:143400,143402:143551,143553:143637,143640:143706,143708:144069,144071:144178,144180:144307,144309:144316,144318:144329,144331:144931,144933:144983,144985:145000,145002:145069,145071:145072,145074:145132,145136:145178,145180:145191,145193 Also, to verify it wasn't something screwy with my server, Michael Slusarz provided me with this from his server: <quote> There's definitely something wonky going on in the code. There's a certain tipping point of modseqs where the values become incorrect. For a mailbox with HIGHESTMODSEQ of 54004, I see this: a uid fetch 1:* UID (VANISHED CHANGEDSINCE 53881) * VANISHED (EARLIER) 1:37308,37310:40788,40791:41032,41034:41083 a OK Fetch completed. b uid fetch 1:* UID (VANISHED CHANGEDSINCE 53882) * VANISHED (EARLIER) 41029:41030,41047:41083 b OK Fetch completed. </quote> Thanks for any guidance. -- mike The Horde Project (www.horde.org) mrubinsk(a)horde.org

4 21

[Dovecot] checkpassword memory limit
by a 08 Jun '14

08 Jun '14

Hi. I am trying to authenticate dovecot from a wordpress database. I was thinking of using the checkpassword script to start a cli php script. That php script would then include the necessary wordpress functions, do the auth (find the wp username from user database using the email address, and authenticate with the user/pass), and return the result to the checkpassword script. I made the above scripts (the php script will be used to authenticate some other services too), and when I run them "by hand" (even with "sudo -u dovecot ..."), it works. But, when the dovecot runs them, the php runs out of memory. After a lot of debuging, I find out that when the dovecot starts the checkpassword script, it makes a 250kB memory limit. But it is not enough for the php script, it needs 14MB. I tried to put a "ulimit -v 16777216" into the checkpassword.sh, but it doesn't work.Is there some hardcoded limit in the dovecot itself? And if there is, could it be somehow changed?I am using a simple D ebian Wheezy LAMP, and installed everything from repo. Thanks for every idea.

2 2

[Dovecot] Authentication Failure (newbie)
by Danny Gorton 08 Jun '14

08 Jun '14

Greetings, I'm am learning about running a mail server and I set up a brand new Ubuntu 14.04 server with postfix and dovecot. I had some initial problems with dovecot not starting, and then with not having proper permissions/access to the various directories and files and pipes, etc, and in the process starting to learn how this thing works. After searching in web-land I seem to have overcome those issues and dovecot and postfix both start and accept connections now (http://wiki2.dovecot.org/TestPop3Installation) However when I check to see if I can authenticate I get Authentication Failed. At the time of these login attempts there are no messages added to syslog or mail.log, dovecot log entries are below. Note I redacted my test user and password values to 'xxxxx', and my domain value to 'domain.com'. Also I'm testing with my plain text password, but I've tried using AUTH PLAIN <base64 encoded uid/pwd>. I have also tried the setup with a default auth domain, and I've tried authenticating with and without the domain name as part of the user name, with the same results. I added the debug settings and disable_plaintext_auth = no to try to solve this issue. Here is my test command set: xxxxx@apacweb:~$ sudo doveadm user xxxxx field valueuserdb lookup: user xxxxx doesn't exist and : xxxxx@apacweb:~$ telnet localhost 110 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Dovecot (Ubuntu) ready. user xxxxx +OK pass xxxxx -ERR [AUTH] Authentication failed. Here is a cut from the dovecot log: 2014-06-08 01:22:10 auth: Error: passwd-file(xxxxx): stat(uid=vmail gid=vmail home=/home/vmail//xxxxx /etc/dovecot/users) failed: Address family not supported by protocol I figure this is the root cause of this issue and the solution to it is supposedly to tell dovecot to not listen on IPv6 (listen = *), but I did that and it didn't help (see config). Here is a cut from the dovecot.info log: 2014-06-08 00:16:25 auth: Debug: auth client connected (pid=3131) 2014-06-08 01:22:10 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth 2014-06-08 01:22:10 auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat 2014-06-08 01:22:10 auth: Debug: passwd-file /etc/dovecot/passwd: Read 1 users in 0 secs 2014-06-08 01:22:10 auth: Debug: master in: USER 1 xxxxx service=doveadm 2014-06-08 01:22:10 auth: Debug: userdb out: NOTFOUND 1 Here is my dovecot config: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain cram-md5 auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no info_log_path = /var/log/dovecot.info listen = * log_path = /var/log/dovecot log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir passdb { args = /etc/dovecot/passwd driver = passwd-file } protocols = imap pop3 service auth { executable = /usr/lib/dovecot/auth unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0777 user = postfix } user = vmail } service imap-login { chroot = login executable = /usr/lib/dovecot/imap-login user = dovecot } service imap { executable = /usr/lib/dovecot/imap } service pop3-login { chroot = login executable = /usr/lib/dovecot/pop3-login inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } user = dovecot } service pop3 { executable = /usr/lib/dovecot/pop3 } ssl = required ssl_cert = </etc/ssl/certs/smtpd.crt ssl_key = </etc/ssl/private/smtpd.key userdb { args = uid=vmail gid=vmail home=/home/vmail/%d/%n /etc/dovecot/users driver = passwd-file } valid_chroot_dirs = /var/spool/vmail protocol pop3 { pop3_uidl_format = %08Xu%08Xv } I'm sure I've done something stupid, but after thrashing about for some days I haven't been able to figure out what it is. Regards, Danny

2 4

Re: [Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13
by Patrick De Zordo 07 Jun '14

07 Jun '14

Same problem here! Updated dovecot some minutes ago from xi.rename-it.nl.. Please resolve it very quick! Having big problems! Thanks, Patrick. > -----Ursprüngliche Nachricht----- > Von: dovecot [mailto:dovecot-bounces@dovecot.org] Im Auftrag von > Thomas Leuxner > Gesendet: Samstag, 7. Juni 2014 17:29 > An: dovecot(a)dovecot.org > Betreff: Re: [Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13 > (feea8645c4d7) > > * Thomas Leuxner <tlx(a)leuxner.net> 2014.06.07 12:15: > > > Latest 2.2.13 HG feea8645c4d7 seems to unexpectedly kill imap-login > sessions: > > I can crash the process at will over a TLS connection with mutt, which I can't > when disabling TLS. So the culprit most-likely is this change: > > http://hg.dovecot.org/dovecot-2.2/rev/09d3c9c6f0ad > > It seems difficult to predict the imap-login process that will crash, hence I > struggle which one to connect GDB to...

1 0

Re: [Dovecot] doveadm index - Bug or expected behaviour?
by Bruno Galindro da Costa 06 Jun '14

06 Jun '14

ok tks! 2014-06-06 3:16 GMT-03:00 Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Thu, 5 Jun 2014, Bruno Galindro da Costa wrote: > > My ldap config is using the variable %d in base search for domain >> replacement when dovecot will search for users in LDAP. Its works fine for >> dovecot operation. >> > > When an user logs into Dovecot, the login process can extract the domain > part from the login username. > > > But, for doveadm index, not. It ignores that variable and tries to pass a >> base search without domain. So, the search will not working. >> >> This is the command: >> # doveadm -v index -A INBOX >> > > If you iterate all users (-A), doveadm would need to guess all domains and > iterate through them. So, in your case you cannot use -A. However, -u > should work. That is, you call the command for each single user that you've > iterated from LDAP via script. > > base = ou=%d,ou=mail,ou=services,dc=domain >> > [...] > > iterate_filter = >> (&(objectclass=nisMailAlias)(ContaAtiva=TRUE)(!(EmailQuota=0))) >> iterate_attrs = rfc822mailmember=user >> > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU5Fcynz1H7kL/d9rAQI7IggAitRJlAU4olmkTzUqXxrxxPAtF0FMcm0c > PqWdByrNM0aLr1WTIShN7y83OnTwFhznuuTg6oVO6s72KZ6Izo9COOK70kLvoGzZ > G4TyNu9S671hDVWsasuI+FvChGZURM+6E4G+ctsqTSjY8N8MV6hEdwrNhxBWbbfE > nQ0BEMDDaM0Qeycyiy59nhlOkLiSkv40P2NnOekkSvogxb3rpxt9FQ6vIrBkCxJd > K1xlwAWzg7Hr4LIUw3PJm0YjT7T4H+1AmiIm7iaAnT8My/9SSB9WCtmFQpzFNWOD > tpKc3RcQJykJMpC4oKjgTi0Vh6PTl6g3xMdA9yJ2jmgpLVqpU2fNKw== > =l3yY > -----END PGP SIGNATURE----- > -- Att. Bruno Galindro da Costa

1 0

[Dovecot] Running dovecot under Cygwin
by Manolis Spanakis 06 Jun '14

06 Jun '14

Hi, In http://wiki2.dovecot.org/DovecotFeatures I found the following statement regarding devcot support of cygwin: Cygwin works after a few code changes, but doesn't support SCM_RIGHTS I downloaded "dovecot-2.2.13.tar.gr" and tried to compile it under cygwin version 1.7.30 (0.272/5/3) CYGWIN_NT-6.3-WOW642.580 (32-bit). As I executed the: $./configure I got the following error: error: fd passing is required for Dovecot to work If I bypass this error by changing "configure" I get no other errors either in "configure" or "make". It seems that "src/lib/fdpass.c" is the only library incompatible with cygwin. Is there any file version available that provides a solution? Thank you in advance, Manolis Spanakis

1 0

[Dovecot] CRAM-MD5 authentication memory leak problem.
by Kenji Tonami 06 Jun '14

06 Jun '14

I used dovecot Auth daemon for postfix SMTP Auth. I saved clear password to OpenLDAP, then I set up that as the password will be used. There ware no trouble when authentication had sucessed. But when authentication failed by using "CRAM-MD5", it caused increasing memory allocation of dovecot auth daemon. In case of using "PLAIN" or "LOGIN", there were no problem even if authentication had failed. I got same result on dovecot-2.0.9(RHEL6) and dovecot-2.2.13. Does anyone know similar case? I tried restarting dovecot Auth daemon by using service_count parameter in service auth settings. When authentication failed, message on postfix was as follows: ** 535 5.7.8 Error: authentication failed: "CRAM-MD5 string" When authentication failed and restarting dovecot auth daemon at the same time, message on postfix was changed as follows: ** 535 5.7.8 Error: authentication failed: Connection lost to authentication server It looks like that the failed authentication request is suspended by restarting auth daemon. -- config (10-auth.conf) auth_mechanisms = plain login cram-md5 -- -- config (10-master.conf) service auth { executable = auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } } -- -- auth-ldap.conf.ext passdb { driver = ldap args = /etc/dovecot/ldap-passdb.conf.ext } -- -- ldap-passdb.conf.ext host = xxx.xxx.xxx.xxx dn = LDAP Manager DN dnpass = Manager DN password base = ou=mail,dc=xxxxxx,dc=xx scope = subtree pass_attrs = mailID=user,mailClearPassword=password pass_filter = (mailID=%u) auth_bind = no default_pass_scheme = plain -- Thanks. -- Kenji Tonami

1 0

Re: [Dovecot] Outlook 2007 & 2010 hangs in v2.2?
by Joseph Tam 06 Jun '14

06 Jun '14

Timo Sirainen <tss(a)iki.fi> writes: > Has anybody noticed Outlook 2007 & 2010 (but apparently not 2013) > hanging IMAP connections with Dovecot v2.2 (but not v2.1) when they're > FETCHing large mails? I can't think of any reasonable explanation for > this. It's a shot in the dark, but I had a problem with a different client, where semi-large attachments was problematic. It turned out to be a TCP scaling problem. If a router/firewall drops packets with a TCP scaling option set, the endpoints disagree on how many outstanding non-ACK packets are allowed, resulting in timeouts. http://support.microsoft.com/kb/935400 http://en.wikipedia.org/wiki/TCP_window_scale_option The Microsoft KB does hint those versions of Outlook may be affected, but I can't figure out why there would be a difference between Dovecot 2.1 and 2.2. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Sharing folder with others
by Claudinei Santos 05 Jun '14

05 Jun '14

Hello, The sharing folders with dovecot works, but when the user that i shared the folder reads any e-mails in the folder, all my subcribed folder (the folders that i do not shared with this user) is unsubcribed from my account. The only folders that remains is the default ones ( inbox, trash, spam and sent) and the folder that i shared with that user. my configurations: # separator for master-users, example: "login_user*master_user -> user(a)domain.tld*masteruser auth_master_user_separator = * passdb passwd-file { driver = passwd-file args = /etc/dovecot-masterusers master = yes } namespace private { type = private separator = / prefix = #location defaults to mail_location. inbox = yes } namespace shared { type = shared separator = / prefix = Share Folders/%%u/ location = maildir:/var/spool/mail/vmail/%d/%%n:INDEX=/var/spool/mail/vmail/%d/%n/shared/%%u subscriptions = yes list = children } # cat /etc/dovecot-postlogin #!/bin/bash export MASTER_USER="$USER" exec /usr/lib64/dovecot/imap "$@" Can someone help me out with this? Thanks in advance.

1 0

[Dovecot] director with multiple instances
by Will Yardley 05 Jun '14

05 Jun '14

I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root@retr01 log]# telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Waiting for authentication process to respond.. Log messages are: Jun 3 16:22:03 retr01 dovecot: pop3-login: Error: Timeout waiting for handshake from auth server. my pid=32152, input bytes=0 Jun 3 16:22:33 retr01 dovecot: pop3-login: Error: Timeout waiting for handshake from auth server. my pid=32152, input bytes=0 Jun 3 16:22:33 retr01 dovecot: director: Fatal: No inet_listeners defined for director service (for standalone keep director_servers empty) Jun 3 16:22:33 retr01 dovecot: master: Error: service(director): command startup failed, throttling Jun 3 16:23:08 retr01 dovecot: pop3-login: Error: Timeout waiting for handshake from auth server. my pid=32152, input bytes=0 Jun 3 16:23:33 retr01 dovecot: pop3-login: Disconnected: Inactivity (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured running dovecot procs are: root 32137 1 0 16:20 ? 00:00:00 /usr/sbin/dovecot -c /etc/dovecot-main.conf root 32145 1 0 16:20 ? 00:00:00 /usr/sbin/dovecot -c /etc/dovecot-director.conf doveconf -n for the two configs (dovecot-main.conf, dovecot-director.conf) are included below. dovecot-sql.conf has: driver = sqlite connect = /etc/dovecot/empty.db password_query = select 'y' as proxy, \ NULL as password, \ 'y' as nopassword, \ case '%a' \ when '110' then '10110' \ when '995' then '10110' \ when '143' then '10143' \ when '993' then '10143' end \ as port; (where empty.db is completely empty; this is just used since there's no other way to handle the port mapping, as described elsewhere on the list). A static proxy setup does work, with the normal imap / pop3 listeners. # 2.0.9: /etc/dovecot-main.conf # OS: Linux 2.6.32-431.11.2.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.5 (Santiago) ext4 auth_username_format = %Ln auth_worker_max_count = 60 base_dir = /var/run/dovecot-main default_client_limit = 4096 default_process_limit = 200 dotlock_use_excl = yes mail_fsync = always mail_location = maildir:/var/spool/maildir/%1Ln/%Ln:INDEX=/mnt/post/cache/%1Ln/%Ln mail_plugins = fts fts_squat quota maildir_very_dirty_syncs = yes mbox_write_locks = fcntl mmap_disable = yes namespace { inbox = yes location = prefix = Mail. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { quota = maildir:User Quota quota_rule = *:storage=40960M:messages=3000000 } service auth-worker { user = $default_internal_user } service imap-login { inet_listener imap { port = 10143 } inet_listener imaps { port = 10993 } service_count = 0 vsz_limit = 128 M } service pop3-login { inet_listener pop3 { port = 10110 } inet_listener pop3s { port = 10995 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = HIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3 ssl_key = </etc/pki/dovecot/private/dovecot.pem syslog_facility = local4 userdb { args = uid=vmail gid=mail home=/var/spool/maildir/%1Ln/%Ln driver = static } protocol imap { mail_max_userip_connections = 24 mail_plugins = fts fts_squat quota imap_quota } protocol pop3 { mail_max_userip_connections = 3 pop3_uidl_format = %f } # 2.0.9: /etc/dovecot-director.conf # OS: Linux 2.6.32-431.11.2.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.5 (Santiago) ext4 auth_username_format = %Ln auth_worker_max_count = 60 base_dir = /var/run/dovecot-director default_client_limit = 4096 default_process_limit = 200 director_doveadm_port = 2888 director_mail_servers = 192.168.1.71 192.168.1.72 192.168.1.73 director_servers = 192.168.1.71 192.168.1.72 192.168.1.73 dotlock_use_excl = yes mail_fsync = always mail_location = maildir:/var/spool/maildir/%1Ln/%Ln:INDEX=/mnt/post/cache/%1Ln/%Ln mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = fts fts_squat quota maildir_very_dirty_syncs = yes mbox_write_locks = fcntl mmap_disable = yes namespace { inbox = yes location = prefix = Mail. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } service auth-worker { user = $default_internal_user } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 2888 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service pop3-login { executable = pop3-login director } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = HIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3 ssl_key = </etc/pki/dovecot/private/dovecot.pem syslog_facility = local4 w

1 3