- dovecot - dovecot.org

[Dovecot] mail-filter cannot work with large email about 700k
by boyd yang 25 Mar '14

25 Mar '14

Hi All I configured dovecot 2.1.7 with mail-filter plugin. It works well for small emails like server k big.(7k) But it failed with larger emails about 700k. The scripts hang out, and the mail-filter-out process does not exist and always in ps. It does not work even I use "cat" in mail-filter-out.sh. Where to set the size limit for mail-filter? Do you know how to fix this? This bug also exists in 2.2.12. Thanks!

1 1

[Dovecot] [LMTP] sieve filter does not drop privilleges?
by kjonca＠o2.pl 25 Mar '14

25 Mar '14

I have (user) sieve filter in my home dir. This filter uses "vnd.dovecot.filter" extension to call some shell scripts. These scrips creates some temporary files. Strange thing: whent sieve is called via dovecot-lda - these files are created by user "kjonca" when sieve is called via lmtp - these files are created by root. Is there any way to drop privilleges where lmtp passing messages to sieve? KJ -- http://wolnelektury.pl/wesprzyj/teraz/

1 0

[Dovecot] Dovecot mail-filter cannot work with large email about 700k
by boyd yang 25 Mar '14

25 Mar '14

Hi All I configured dovecot 2.1.7 with mail-filter plugin. It works well for small emails like server k big.(7k) But it failed with larger emails about 700k. The scripts hang out, and the mail-filter-out process does not exist and always in ps. It does not work even I use "cat" in mail-filter-out.sh. Where to set the size limit for mail-filter? Do you know how to fix this? This bug also exists in 2.2.12. Thanks!

1 0

[Dovecot] Disconnected (auth failed, 1 attempts)
by ldaamandy 25 Mar '14

25 Mar '14

hi : i just install dovecot-2 and start ok but login failed for test-user . i turn on all debug options , the debug info follow: "Mar 25 14:40:10 cs2c dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=<q1(a)t.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured" and the info of input->w_buffer is : cp01 CAPABILITY a001 LOGIN "q1(a)t.com" "q1q1q1q1" the auth of dovecot.conf: >>>>>>>>>>>>>>>>>>>>> passdb { args = /etc/dovecot.master driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot-memcached.conf driver = dict } userdb { args = /etc/dovecot-memcached.conf driver = dict } [root@cs2c log]# telnet 127.0.0.1 11211 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. get q1(a)t.com_imap VALUE q1(a)t.com_imap 0 205 {"username":"q1(a)t.com","password":"{CRYPT}$1$d5ef98b7$brWKOJiUiqII3DysGzsfl\/","home":"\/test\/mail","mail":"maildir:\/t.com\/q1@t.com","quota_rule2":"*:messages=11111","quota_rule":"*:bytes=11650727936"} END >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The relevant code is: >>>>>>>>>>>>>login-common/client-common.c<<<<<<< bool client_read(struct client *client) { switch (i_stream_read(client->input)) { //w_buffer:cp01 CAPABILITY a001 LOGIN "q1(a)t.com" "q1q1q1q1" case -2: /* buffer full */ client_send_line(client, CLIENT_CMD_REPLY_BYE, "Input buffer full, aborting"); client_destroy(client, "Disconnected: Input buffer full"); return FALSE; case -1: /* disconnected */ client_destroy(client, "Disconnected"); //debug infomation return FALSE; case 0: /* nothing new read */ return TRUE; default: /* something was read */ return TRUE; } } >>>>>>>>>>imap-login/client.c<<<<<<<<<< static void imap_client_input(struct client *client) { struct imap_client *imap_client = (struct imap_client *)client; if (!client_read(client)) return; client_ref(client); o_stream_cork(imap_client->common.output); for (;;) { if (!auth_client_is_connected(auth_client)) { /* we're not currently connected to auth process - don't allow any commands */ client_send_line(client, CLIENT_CMD_REPLY_STATUS, AUTH_SERVER_WAITING_MSG); if (client->to_auth_waiting != NULL) timeout_remove(&client->to_auth_waiting); client->input_blocked = TRUE; break; } else { if (!client_handle_input(imap_client)) break; } } o_stream_uncork(imap_client->common.output); client_unref(&client); } >>>>>>>>>>>>>>other-dovecot.conf>>>>>>>>>>>>>>>>>>>>>>>>>>>> .......... protocols = pop3 imap service auth { unix_listener /var/spool/postfix/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = testmail mode = 0666 user = testmail } user = testmail } service imap-login { service_count = 1 } service imap { drop_priv_before_exec = no executable = /usr/libexec/dovecot/imap } service pop3-login { service_count = 1 } service pop3 { drop_priv_before_exec = yes executable = /usr/libexec/dovecot/pop3 } ssl_cert = </etc/pki/NSMail/SSL.cert ssl_key = </etc/pki/NSMail/SSL.key userdb { args = /etc/dovecot-memcached.conf driver = dict } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/sieve.log mail_plugins = menc sieve quota acl expire postmaster_address = root } protocol imap { mail_plugins = quota imap_quota zlib mdec imap_acl acl autocreate expire } #protocol vipimap { # mail_plugins = quota imap_quota zlib mdec imap_acl acl autocreate expire #} protocol pop3 { mail_plugins = quota zlib mdec expire pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_no_flag_updates = yes pop3_uidl_format = %08Xu%08Xv }

1 0

[Dovecot] Weird Authentication behaviour
by Jürgen Ladstätter 24 Mar '14

24 Mar '14

Hi guys, we use dovecot 2.0.9 and authentication against a mysql database. Everything works fine, but we found some weird behavior when the password is e.g. testpass you also authenticate successfully with testpass123 or testpassNOT. Whatever comes after the correct password doesnt matter, the authentication is still successful. Here are the used configs: // auth-sql.conf.ext passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } userdb { driver = static args = uid=vmail gid=vmail home=/data/mail/%d/%n } // dovecot-sql.conf.ext driver = mysql connect = host=[IP] dbname=[DB] user=[USER] password=[PASS] default_pass_scheme = CRYPT password_query = SELECT `password`, `login` AS `user` FROM `v_email_accounts` WHERE `login`='%u' // 10-auth.conf disable_plaintext_auth = no auth_mechanisms = plain !include auth-sql.conf.ext // 10-master.conf default_process_limit = 1000 default_client_limit = 3003 default_vsz_limit = 1024M service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 0 vsz_limit = 1024M } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service lmtp { unix_listener lmtp { } } service imap { vsz_limit = 1024M process_limit = 2048 } service pop3 { process_limit = 2048 } service auth { unix_listener auth-userdb { user = vmail group = vmail } client_limit = 8096 } service auth-worker { } service dict { unix_listener dict { } } Thanks in advance for your help!

4 3

[Dovecot] imap: Error: mmap() failed with file ... dovecot.index.cache: Cannot allocate memory
by Urban Loesch 24 Mar '14

24 Mar '14

Hi, since some days (about 10) I get the following error in mail error log many, many times: ... dovecot: imap(user(a)domain.com pid:32769 session:<dszL7lX1xADD/uGI>): Error: mmap() failed with file /home/dovecotindex/domain.com/user/mailboxes/Trash /dovecot.index.cache: Cannot allocate memory .... It's always the same "dovecot.index.cache" file and only for the same heavily used account. The account is currently used from about 10 different clients with imap at the sime time. I checked the size of the index cache file and it seems very big: total 2,7G -rw------- 1 mailstore mailstore 464 Mär 24 14:36 dovecot.index -rw------- 1 mailstore mailstore 464 Mär 24 14:36 dovecot.index.backup -rw------- 1 mailstore mailstore 2,7G Mär 24 14:19 dovecot.index.cache -rw------- 1 mailstore mailstore 140 Mär 24 14:45 dovecot.index.log -rw------- 1 mailstore mailstore 89K Mär 24 14:36 dovecot.index.log.2 About 2,7 GB? To solve the problem temporarily, I removed the index files from the index Trash folder and Dovecot initialized an index rebuild. Now the size of the index files are small: total 28K -rw------- 1 mailstore mailstore 512 Mär 24 14:47 dovecot.index -rw------- 1 mailstore mailstore 20K Mär 24 15:28 dovecot.index.cache -rw------- 1 mailstore mailstore 1,2K Mär 24 15:28 dovecot.index.log But why could the index cache file be so big? Many thanks Urban

1 0

[Dovecot] Dovecot/Django authentication
by Thomas Johnson 24 Mar '14

24 Mar '14

We've got an application in django that has passwords stored in both sha1 and pbkdf2_sha256 form. We need dovecot to be able to authenticate against the django database (we can't modify django to store passwords in dovecot's form, I'm afraid). Has anyone done a dovecot authentication plugin to support these password forms (and/or any other forms that django supports)? Thanks- Tom

2 1

[Dovecot] Case-sensitive INBOX or client issue?
by SB Code Ninja 24 Mar '14

24 Mar '14

I am using dovecot as an IMAP server for a Cisco product (Cisco Agent Desktop by Calabrio) and noticed some odd behavior when trying to access emails. The mail is delivered to the main INBOX, then a Cisco server moves it to a directory within the INBOX based on the queue it is meant for. Here is the directory structure of the Maildir: Maildir/INBOX Maildir/INBOX/tmp Maildir/INBOX/63 Maildir/INBOX/63/tmp Maildir/INBOX/63/dovecot.index.cache Maildir/INBOX/63/cur Maildir/INBOX/63/cur/1395445673.M548066P32100.uc-util,S=6403:2, Maildir/INBOX/63/dovecot.index.log Maildir/INBOX/63/dovecot-uidlist Maildir/INBOX/63/maildirfolder Maildir/INBOX/63/new Maildir/INBOX/dovecot.index.cache Maildir/INBOX/cur Maildir/INBOX/dovecot.index.log Maildir/INBOX/dovecot-uidlist Maildir/INBOX/62 Maildir/INBOX/62/tmp Maildir/INBOX/62/dovecot.index.cache Maildir/INBOX/62/cur Maildir/INBOX/62/cur/1395445491.M591207P32114.uc-util,S=6380:2, Maildir/INBOX/62/dovecot.index.log Maildir/INBOX/62/dovecot-uidlist Maildir/INBOX/62/maildirfolder Maildir/INBOX/62/new Maildir/INBOX/new Email is delivered to INBOX then gets moved to INBOX/62 or INBOX/63. The desktop software is then supposed to read the email and process it. I did a packet capture of the conversation and saw the following: IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. IMAP Request: A0 AUTHENTICATE PLAIN IMAP Response: + IMAP Request: <redacted> IMAP Response: A0 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in IMAP Request: A1 LIST "" Inbox/63 IMAP Response: A1 OK List completed. IMAP Request: A2 CREATE Inbox/63 IMAP Response: A2 NO [ALREADYEXISTS] Mailbox exists. If I login manually and do 'LIST "" INBOX/63' it works fine, but not with "Inbox/63". I was under the impression that INBOX was not case-sensitive. Is this a bug or is the client doing something silly? Thanks, Henry dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.7 disable_plaintext_auth = no mail_location = maildir:~/Maildir:LAYOUT=fs namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" ssl = no ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } -- "The best way to predict the future is to invent it" - Alan Kay

3 2

[Dovecot] dsync in a cronjob to replace offlineimap
by Guilhem Moulin 24 Mar '14

24 Mar '14

Hi list, Replacing offlineimap with dsync for IMAP-to-IMAP synchronization (using dovecot 2.1.7) is working great, but now that I upgraded to 2.2.9 I'd like to take advantage of the incremental replication [1]. I don't think having a separate replicator process & notifications suits my configuration, as I want to sync my server with my laptop which is not always on or might be behind a firewall. After reading ‘replication/replicator/dsync-client.c’ I was thinking of writing a small wrapper around dsync performing a daily full replication and updating the state otherwise. The following works great in a cronjob doveadm sync -l30 imap.example.org but when I try to get the current state doveadm sync -l30 -fs '' imap.example.org >~/mail/dsync.state and later use incremental replication state=$(< ~/mail/dsync.state) doveadm sync -l30 -s "$state" imap.example.org >~/mail/dsync.state the state seems to somehow quickly become "stale" and messages stop being retrieved from the server. I understand that dsync's incremental replication is mostly intended to be used by the replicator process, but I'm wondering whether it's also possible to use it manually ;-) If so, how to keep a sane state? Thanks, cheers, -- Guilhem. [1] http://wiki2.dovecot.org/Replication

2 1

[Dovecot] Where can I find a stable PPA?
by Daniel Reynolds 22 Mar '14

22 Mar '14

Hello, As the subject says, where can I find a stable PPA of Dovecot v2.2 for Ubuntu 12.04? I found this <https://launchpad.net/~kokelnet/+archive/dovecot22>, but the description says, "...I declare them as unstable." For obvious reasons, I don't want to use this. What should I do? Thanks, Daniel

4 4