- dovecot - dovecot.org

[Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13 (feea8645c4d7)
by Thomas Leuxner 10 Jun '14

10 Jun '14

Latest 2.2.13 HG feea8645c4d7 seems to unexpectedly kill imap-login sessions: Jun 7 11:56:10 nihlus dovecot: imap(tlx(a)leuxner.net): Disconnected: Logged out in=2203 out=851225 Jun 7 11:56:10 nihlus dovecot: imap(tlx(a)leuxner.net): Disconnected: Logged out in=316 out=2417 Jun 7 11:56:10 nihlus dovecot: imap-login: Fatal: master: service(imap-login): child 60505 killed with signal 11 (core not dumped - add -D parameter to service imap-login { executable } Jun 7 11:56:10 nihlus dovecot: imap-login: Fatal: master: service(imap-login): child 60595 killed with signal 11 (core not dumped - add -D parameter to service imap-login { executable } Adding the -D parameter does not generate a core dump however...

5 7

Dovecot auth NTLM
by dovecot.lista＠palacio.cu 10 Jun '14

10 Jun '14

Hello, this is my first email to the list... i´m configuring Dovecot with NTLM authentication, at least this is what i wanted, but i´m having a few problems. 1-I made my configuration following the steps from this howto http://wiki2.dovecot.org/HowTo/ActiveDirectoryNtlm from the dovecot official site, but my dovecot´s version is 2.1.7 and the tutorial dovecot´s version is 1.1.16. But, the fact is that when i enter to the wiki1, for the version 1.x i found that all the howtos are obsoletes and the tutorial for the version 1.x is the same for the 2.x version, so this howto is not trustful.... but, there is not another one. 2-When i implement it all seems to work OK, but the communication between dovecot and the helper in "/usr/bin/ntlm_auth". I made the tests with the binary(/usr/bin/ntlm_auth) and i got the right answers from it, and i also made the test with the tool wbinfo and were successful. During the tests i was monitoring the logs of my Domain Controller (The server from where i want to authenticate) and it logged all the requests i made however when i try to authenticate with dovecot in my Domain Controller nothing is written in the logs... then i get to the conclusion that Dovecot is not communicating with the helper, and of course in dovecot´s logs appears: auth: Info: winbind(?,10.10.10.10): user not authenticated: NT_STATUS_UNSUCCESSFUL As i said, my friends, there is no any other tutorial or howto in internet, at least i did not see it. I´m asking for your help... if any of you have configured Dovecot to auth against NTLM, please tell me how. Im working on Debian Wheezy and Dovecot 2.1.7. PS:Please forgive my English i speak Spanish

1 0

Dovecot Configuration for access with GSSAPI / Kerberos
by Sandra 10 Jun '14

10 Jun '14

Hi Dovecot-Mailinglist! I try to install a new Dovecot-Server with Kerberos-Authentification (Kerberos-Server is already authenticating user-account ). The following error-notice occurs when I use mail-programm Gnome Evolution to access IMAP-Account: "Ordner konnte nicht geöffnet werden (Folder can not be opened) The reported error was "GSSAPI-Legitimation ist fehlgeschlagen". (GSSAPI-Legitimation failed) Is anybody able to help me??? Thanks in advance, Sandra Dovecot Version: 2.1.17 Configuration: auth_mechanisms = gssapi auth_debug = yes auth_gssapi_hostname = kerberosServer.domain auth_realms = REALM auth_default_realm = REALM auth_krb5_keytab = /etc/krb5.keytab auth_verbose = yes disable_plaintext_auth = yes userdb { driver = static args = uid=vmail gid=vmail home=/service/mailServer_Kommunikations-Server/mails/%u } mail_location = maildir:/service/mailServer_Kommunikations-Server/mails/imap/% u/:INBOX=/service/mailServer_Kommunikations-Server/mails/maildir/%u log_timestamp = "%Y-%m-%d %H:%M:%S " managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave protocols = imap pop3 ssl = no service auth { unix_listener /var/spool/postfix/private/auth_dovecot { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = mail } user = root } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master postmaster_address = root(a)mailServer.domain } mail_privileged_group = mail Logfile: 2014-06-09T09:59:22.596608+02:00 highlands dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/modules/auth 2014-06-09T09:59:22.598243+02:00 highlands dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_mysql.so 2014-06-09T09:59:22.598559+02:00 highlands dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/modules/auth 2014-06-09T09:59:22.600354+02:00 highlands dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libmech_gssapi.so 2014-06-09T09:59:22.600982+02:00 highlands dovecot: auth: Debug: auth client connected (pid=5770) 2014-06-09T09:59:22.602211+02:00 highlands dovecot: auth: Debug: client in: AUTH#0111#011GSSAPI#011service=imap#011session=E7rSlmL70wDAqEWd#011lip=mailServerIP#011rip=clientIP#011lport=143#011rport=46035 2014-06-09T09:59:22.602498+02:00 highlands dovecot: auth: Debug: gssapi(?,clientIP,<E7rSlmL70wDAqEWd>): Obtaining credentials for imap(a)dartmoor.outback 2014-06-09T09:59:22.610815+02:00 highlands dovecot: auth: gssapi(?,clientIP,<E7rSlmL70wDAqEWd>): While acquiring service credentials: Unspecified GSS failure. Minor code may provide more information 2014-06-09T09:59:22.611097+02:00 highlands dovecot: auth: gssapi(?,clientIP,<E7rSlmL70wDAqEWd>): While acquiring service credentials: No key table entry found matching imap/dartmoor.outback@ 2014-06-09T09:59:24.113071+02:00 highlands dovecot: auth: Debug: client passdb out: FAIL#0111#011temp 2014-06-09T09:59:24.113818+02:00 highlands dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<>, method=GSSAPI, rip=clientIP, lip=mailServerIP, session=<E7rSlmL70wDAqEWd>

1 0

Bug when virtual mailbox is set to auto=subscribe
by Daniel Neugart 10 Jun '14

10 Jun '14

Hi everybody, I'd like to submit a bug: My setup: dovecot version: 2.2.13-1 Kernel: 3.14.5-1-ARCH on arch linux x64 Filesystem: ext4 Bug description: If a virtual mailbox is defined with auto = subscribe dovecot crashes upon access via imap. Configuration is as followed: namespace inbox { [...] mailbox virtual/Flagged { auto = subscribe special_use = \Flagged } [...] dovecot-virtual file: # ~/Maildir/virtual/Flagged/dovecot-virtual * -Trash -Trash/* flagged 'auto' must be set to 'no' for virtual mailboxes, otherwise dovecot crashes when the virtual folder is tried to be accessed via a imap (thunderbird in my case). Crash log: Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Panic: file mail-index-sync.c: line 413 (mail_index_sync_begin_to2): assertion failed: (!index->syncing) Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x68680) [0x7fa67a692680] -> /usr/lib/dovecot/libdovecot.so.0(+0x6876c) [0x7fa67a69276c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa67a64c83d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc3dfe) [0x7fa67a9c3dfe] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x3f) [0x7fa67a9c3eaf] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1c) [0x7fa67a9c3f3c] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xc3) [0x7fa679e71d23] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf94) [0x7fa679e72bf4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf94) [0x7fa679e72bf4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> dovecot/imap(imap_status_get+0x67) [0x41d6f7] -> dovecot/imap(cmd_status+0x188) [0x4131c8] -> dovecot/imap(command_exec+0x3c) [0x4171ac] -> dovecot/imap() [0x416202] Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Fatal: master: service(imap): child 24926 killed with signal 6 (core dumped) Below a complete dump of doveconf -n (with corrected 'auto' value for virtual mailboxes): # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.14.5-1-ARCH x86_64 mail_home = /home/vmail/%d/%n mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = " virtual" namespace { location = virtual:~/Maildir/virtual prefix = virtual/ separator = / } namespace inbox { inbox = yes location = mailbox Archive { auto = create special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } mailbox virtual/Flagged { auto = no special_use = \Flagged } prefix = } passdb { args = username_format=%n scheme=SHA512-CRYPT /etc/dovecot/%d/passwd driver = passwd-file } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } ssl_cert = </$PATH to my ssl cert ssl_key = </$PATH to my ssl key userdb { args = username_format=%n /etc/dovecot/%d/passwd default_fields = uid=vmail gid=vmail driver = passwd-file } protocol lmtp { postmaster_address = postmaster(a)mydomain.com } Best regards Daniel

1 0

[Dovecot] NoSQL support
by List 09 Jun '14

09 Jun '14

Is there any support for NoSQL databases such as Cassandra (CQL) or MongoDB now or planned in the future for userdb and passdb lookups?

2 1

[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