- dovecot - dovecot.org

[Dovecot] Dovecot 2.0 zlib and dbox
by Renaud Allard 30 Mar '10

30 Mar '10

Hello, As per wiki instructions, I tried to enable zlib compression of mails by adding/modifying the following snippets of configuration: plugin { zlib_save_level = 6 zlib_save = gz } and protocol imap { mail_plugins = fts fts_squat autocreate zlib imap_zlib imap_id_log = * } I am using dbox format and delivering the mails via dovecot deliver, however mails don't seem compressed at all. It is not very clear if compression is available for something else than maildir and mbox, so is compression available with dbox format? I am using dovecot-2-0-aefa279e2c70 from hg. Best Regards

2 3

[Dovecot] Dovecot 2.0beta4 HG 11014: Crashes on parsing settings via LMTP service
by Thomas Leuxner 29 Mar '10

29 Mar '10

Hi, unfortunately no core was dumped. Let me know if you need more info to debug. ==> /var/log/dovecot.log <== Mar 27 08:13:38 spectre dovecot: lmtp(8362): Connect from local Mar 27 08:13:38 spectre dovecot: lmtp(8362): Panic: file settings-parser.c: line 1501 (settings_link_get_new): assertion failed: (diff + sizeof(*old_link->array) <= old_link->parent->info->struct_size) Mar 27 08:13:38 spectre dovecot: lmtp(8362): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f055dec6712] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f055dec677a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f055dec6b23] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f055dea6993] -> /usr/lib/dovecot/libdovecot.so.0(settings_parser_dup+0x1d2) [0x7f055dea6be2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup+0x191) [0x7f055e1370c1] -> dovecot/lmtp(cmd_rcpt+0x4d4) [0x407924] -> dovecot/lmtp(client_input_handle+0x19b) [0x4066db] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xcb) [0x7f055ded144b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f055ded05c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f055dec0323] -> dovecot/lmtp(main+0x123) [0x405bf3] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f055d74d1a6] -> dovecot/lmtp [0x4059f9] Mar 27 08:13:38 spectre dovecot: master: service(lmtp): child 8362 killed with signal 6 (core not dumped) Regards Thomas

3 6

[Dovecot] dovecot: auth(default): Fatal: Unknown database driver 'mysql'
by Glen Lee Edwards 29 Mar '10

29 Mar '10

I just tried upgrading from 1.1.rc6 to v1.2.11, and am getting the following error: dovecot: auth(default): Fatal: Unknown database driver 'mysql'. If I change the respective line in dovecot-sql.conf from driver = mysql to driver = pgsql the error message changes accordingly: dovecot: auth(default): Fatal: Unknown database driver 'pgsql'. I quit using 1.1.rc6 because it started choking on my Debian system, so I'm back to using the stable Debian version - 1:1.0.15-2.3+lenny1. Where are the drivers kept when I do a default build, and where in the configuration file does it tell dovecot to look for the drivers? Other suggestions on a fix? Glen

3 7

[Dovecot] Which Authentication Method Best Between FreeBSD and Macintosh?
by Martin McCormick 29 Mar '10

29 Mar '10

I recently discovered that I need to occasionally forward Email from a FreeBSD system to a Macintosh. Imap does look like the best solution to this problem. The mail program on the Mac lists several protocols such as pop (okay with me) and SSL certificates which I want to avoid if at all possible. Which of the several listed methods of authentication should I compile in as I build dovecot on the FreeBSD system? Options for dovecot 1.2.10 [X] KQUEUE kqueue(2) support [ ] SSL SSL support [ ] IPV6 IPv6 support [ ] MANAGESIEVE ManageSieve support [ ] GSSAPI GSSAPI support [ ] VPOPMAIL VPopMail support [ ] BDB BerkleyDB support [ ] LDAP OpenLDAP support [ ] PGSQL PostgreSQL support [ ] MYSQL MySQL support [ ] SQLITE SQLite support � � IPV6 is not used here and my laziness says to avoid creating any new data bases or data base servers to support something I will probably use once every 2 or 3 months for one or 2 messages. I just want to get on the Mac and read messages posted in a certain account on the FreeBSD system. Sorry if this all sounds a bit odd, but I usually read mail on the FreeBSD box. Occasionally, I get a message containing a 20-mile-long URL that works better when using the Mac's safari browser tools. Presently, I have succeeded in compiling dovecot on the freeBSD system which runs and looks like it is ready to work. The Mac contacts the freeBSD box and then both appear to get a death grip on each other and nothing much happens until I force a quit of mail on the Mac. Thanks for any suggestions. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group

1 0

Re: [Dovecot] I stream read - stale NFS file handle (reboot of server)
by Damon Atkins 29 Mar '10

29 Mar '10

NFS Security 101 for NFSv2 and v3 (NOT NFSv4 a long time ago I was part of the discussion group for NFSv4 spec the short comings of v2 and v3 have been fixed) SRV: Server Exports File System /abc/123 access only to host=xyz.domain.com XYZ: Client Mount mount's SRV:/abc/123 SRV: "mountd" gets a request from SRV check access list, and if the client is allowed access, returns File Handle for the top of the mount point (I will call this the FileSystemHandle, this changes after every reboot) XYZ: Client talks to the SRV NFS Server "nfsd" using FileSystemHandle (which represents /abc/123), To find a FileHandle for a file the client sends the NFS server the FileSystemHandle, then finds the next File Handle (/mydir) and the next FileHandle (myfile) and the client has found the FileHandle for /abc/123/mydir/myfile NFSD (v2/v3) is stateless other than the information provided by mountd (mount requests) and lockd (file locking). When you share/export a file system, as part of this a FileSystemHandle is generated and stored somewhere for /abc/123 most likely store in the kernel. SRV: Reboots, a new FileSystemHandle is allocated XYZ: Reports Stale File Handle for everything (if not most things) which was mounted from SRV or the mount point on the client does not respond. A long time ago FileSystemHandle would stay the same between reboots and you wouldn't get this problem other than on an individual file. To handle deleted files which are in use by NFS clients some servers rename them to .nfs* because if one client deleted and other clients where accessing the file then they would get Stale NFS handle. Once in a while a NFS server will do find $dir -type f -name .nfs\* -mtime +7 -mount -exec rm -f {} \; to clean up. NFSv4 does not use mountd or lockd. My advice to anyone on old versions of NFS upgrade to NFSv4 as soon as possible and implement KerbV5 for improved authentication and disallow NFSv2/3 access. If you do not get the Stale File Handle error when the server reboots, it most likely means the FileSystemHandle is not changing between reboots, but then you may have more security issues. Software which Clusters NFS Servers ensures that the node which takes over, uses the same FileSystemHandle (which may only change if the whole Cluster is shutdown) Cheers Damon.

2 4

[Dovecot] failed: Too many open files
by Masaharu Kawada 29 Mar '10

29 Mar '10

Dear list, I have questions about content of the following error messages. ---</var/log/secure>--- dovecot-auth:　PAM　unable　todlopen(/lib/security/pam_nologin.so) dovecot-auth:　PAM　[error:/lib/security/pam_nologin.so:　cannot　open　shared　object　file:　Too　many　open　files] dovecot-auth:　PAM　adding　faulty　module:/lib/security/pam_nologin.so dovecot-auth:　PAM　_pam_load_conf_file:　unable　to　open　/etc/pam.d/system-auth dovecot-auth:　PAM　unable　to　dlopen(<*unknown　module　path*>) dovecot-auth:　PAM　[error:　*unknown　module　path*>:　cannot　open　shared　object　file:　Too　many　open　files] dovecot-auth:　PAM　adding　faulty　module:　<*unknown　module　path*> dovecot-auth:　PAM　_pam_load_conf_file:　unable　to　open　/etc/pam.d/system-auth dovecot-auth:　PAM　_pam_load_conf_file:　unable　to　open　/etc/pam.d/system-auth dovecot-auth:　PAM　unable　to　dlopen(/lib/security/pam_deny.so) dovecot-auth:　PAM　[error:/lib/security/pam_deny.so:　cannot　open　shared　object　file:　Too　many　open　files] dovecot-auth:　PAM　adding　faulty　module:/lib/security/pam_deny.so ---</var/log/maillog>--- dovecot: auth(default): pam(xxx(a)xxx.com,127.0.0.1): pipe() failed: Too many open files dovecot: auth(default): pam(xxx(a)xxx.com,127.0.0.1): pipe() failed: Too many open files It seems that this is due to that there are files existed to open beyond its limitation. Other information that could be relevant are as follows. # ulimit -n 1024 # cat /proc/`cat /var/run/dovecot/master.pid`/limits cat: /proc/7273/limits: No such file or directory # lsof -p `cat /var/run/dovecot/master.pid` | wc -l 29 # ls /proc/`pidof dovecot-auth`/fd | wc -l 1024 >From the above result, dovecot-auth proccess opened 10243 files, and that seems to be the limit. So I expect that adding following lines into /etc/init.d/dovecot could be fix this issue. # vi /etc/init.d/dovecot --- . /etc/init.d/functions ulimit -n 4098 <-add test -x /usr/sbin/dovecot || exit 0 <-add if [ -f /etc/sysconfig/dovecot ]; then . /etc/sysconfig/dovecot fi --- Is my understanding right? Even if so, how could I verify what files are opened by dovecot-auth? I would very much appreciate it if someone in this list could provide comments/suggestions. Sincerely,

3 6

[Dovecot] Improper use of IN-USE in case of a failed authentication
by Rainer Weikusat 29 Mar '10

29 Mar '10

RFC2449 defines the IN-USE extended POP3 response code as 8.1.2. The IN-USE response code This occurs on an -ERR response to an AUTH, APOP, or PASS command. It indicates the authentication was successful, but the user's maildrop is currently in use (probably by another POP3 client). http://www.faqs.org/rfcs/rfc2449.html In contrast to this, the POP3 login code in client_authenticate.c will send IN-USE whenever authentication was not successful because of some kind of internal failure[*]. [*] Noticed during experiments with a shell SQL database driver which only ever returns errors as reaction to any query. I happen to know of at least one (partial) client implementation (I happen to have written which is used by an iPhone application for POP3 user credential verification) which actually interprets IN-USE as it is defined by the RFC.

2 2

[Dovecot] dsync multiserver
by Renaud Allard 28 Mar '10

28 Mar '10

Hello, Maybe I am missing something obvious here (I would hope so), but is there any way to use dovecot deliver to spawn dsync to replicate changes. And dovecot to trigger dsync to sync mailboxes when a change has been done. Thanks

2 1

[Dovecot] permanent flags (are very permanent)
by Oliver Eales 28 Mar '10

28 Mar '10

Hello, first of all i am not sure wheter this is a correct behavior according to the RFC or not... Problem is, when i set a new custom permanent flag (e.g. testflag) and remove it afterwards, the flag still stays in the list of the permanent flags of this drawer even if there are no messages left with this flag set. So the keyword list gets "polluted" with unused flags. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] uc.vodafone.de Mailservices ready. AA login user notmypass AA 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 QUOTA] Logged in A0 SELECT inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk \*)] Flags permitted. * 3805 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1260979519] UIDs valid * OK [UIDNEXT 4465] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest A0 OK [READ-WRITE] Select completed. A1 STORE 1 +FLAGS (testflag) * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk testflag) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk testflag \*)] Flags permitted. * 1 FETCH (FLAGS (Junk testflag)) A1 OK Store completed. A2 SEARCH KEYWORD testflag * SEARCH 1 A2 OK Search completed (0.043 secs). A3 STORE 1 -FLAGS (testflag) * 1 FETCH (FLAGS (Junk)) A3 OK Store completed. A4 select inbox * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk testflag) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk testflag \*)] Flags permitted. * 3805 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1260979519] UIDs valid * OK [UIDNEXT 4465] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest A4 OK [READ-WRITE] Select completed. So the new testflag keyword is now in the list even across logins. Regards, Oliver Eales

2 3

[Dovecot] Fix for the consume_results leak
by Rainer Weikusat 28 Mar '10

28 Mar '10

I'm not really comfortable with making non-trivial changes to this code but here is at least a fix for the PGresult leak (verified to both apply to 1.2.11 and 2.0.beta4). ----- --- dovecot/src/lib-sql/driver-pgsql.c 15 Mar 2010 18:18:14 -0000 1.1.1.2 +++ dovecot/src/lib-sql/driver-pgsql.c 26 Mar 2010 14:13:18 -0000 1.1.1.2.4.1 @@ -247,6 +247,17 @@ return 0; } +static inline int more_results(PGconn *pg) +{ + PGresult *pgres; + + pgres = PQgetResult(pg); + if (!pgres) return 0; + + PQclear(pgres); + return 1; +} + static void consume_results(struct pgsql_db *db) { do { @@ -255,7 +266,7 @@ if (PQisBusy(db->pg)) return; - } while (PQgetResult(db->pg) != NULL); + } while (more_results(db->pg)); if (PQstatus(db->pg) == CONNECTION_BAD) io_remove_closed(&db->io);

2 2

[Dovecot] convert v1.2 config to v2.0
by Odhiambo Washington 27 Mar '10

27 Mar '10

How do I convert a version 1.2.x config into a v2.0 config? Some command? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube

2 1

[Dovecot] INBOX. namespace
by Brian Candler 27 Mar '10

27 Mar '10

I am trying to configure dovecot-1.2.11 to have the same IMAP namespacing as courier-imap as per http://wiki.dovecot.org/Migration/Courier, but failing badly. I have a test maildir with INBOX and folder 'junk'. Without fiddling with namespaces, this works fine: there are 91 msgs in INBOX and 2 in junk. a namespace * NAMESPACE (("" ".")) NIL NIL a OK Namespace completed. a examine INBOX ... * 91 EXISTS ... a OK [READ-ONLY] Select completed. a examine junk ... * 2 EXISTS ... a OK [READ-ONLY] Select completed. Now I make the following addition to dovecot.conf: namespace private { separator = . prefix = INBOX. inbox = yes hidden = no } After this the inbox appears to be empty, and I cannot select the junk folder at all: a namespace * NAMESPACE (("INBOX." ".")) NIL NIL a OK Namespace completed. a examine INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1269605071] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest a OK [READ-ONLY] Select completed. a examine INBOX.junk * OK [CLOSED] Previous mailbox closed. a NO Mailbox doesn't exist: junk Furthermore I can select "INBOX.INBOX" (although that's empty as well) a examine INBOX.INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1269605071] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest a OK [READ-ONLY] Select completed. a examine INBOX.INBOX.INBOX * OK [CLOSED] Previous mailbox closed. a NO Mailbox doesn't exist: INBOX.INBOX a examine junk a NO Unknown namespace. Have I misunderstood what I'm supposed to be doing here? The other relevant setting is: mail_location: maildir:%h but I've not changed this; as I say, this works just fine without meddling with namespaces. Many thanks, Brian.

2 4

[Dovecot] Dovecot 2.0beta4 changset 11014 dict: Panic: file driver-mysql.c
by e-frog 27 Mar '10

27 Mar '10

Hi, With the latest hg version I see panics with dict process whenever a message is received via lmtp. This didn't happen with the original beta4 release. Mar 27 11:45:51 ubuntu-test dovecot: dict: mysql: Connected to localhost (mails) Mar 27 11:45:51 ubuntu-test postfix/lmtp[5261]: 0F22B27F0D: to=<test(a)ubuntu-test.localdomain>, orig_to=<test(a)ubuntu-test.localdomain>, relay=ubuntu-test.localdomain[dovecot-lmtp], delay=0.41, delays=0.06/0.01 /0.22/0.11, dsn=2.0.0, status=sent (250 2.0.0 <test(a)ubuntu-test.localdomain> WsNlE9/hrUuOFAAA7I0XzQ Saved) Mar 27 11:45:51 ubuntu-test dovecot: master: service(dict): child 5263 killed with signal 6 (core not dumped) Mar 27 11:45:51 ubuntu-test dovecot: master: service(dict): command startup failed, throttling Mar 27 11:45:51 ubuntu-test dovecot: lmtp(5262, test): WsNlE9/hrUuOFAAA7I0XzQ: sieve: msgid=<4BADE1E9.7000709(a)ubuntu-test.localdomain>: from=test(a)ubuntu-test.localdomain: stored mail into mailbox 'INBOX' Mar 27 11:45:51 ubuntu-test dovecot: dict: Panic: file driver-mysql.c: line 633 (transaction_send_query): assertion failed: (rows != (my_ulonglong)-1) Mar 27 11:45:51 ubuntu-test dovecot: dict: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb773dd92] -> /usr/lib/dovecot/libdovecot.so.0 [0xb773ddff] -> /usr/lib/dovecot/libdovecot.so.0(i_erro r+0) [0xb77198ee] -> dovecot/dict [0x80506aa] -> dovecot/dict [0x80506e6] -> dovecot/dict(sql_transaction_commit_s+0x20) [0x804f730] -> dovecot/dict [0x804de42] -> /usr/lib/dovecot/libdovecot.so. 0(dict_transaction_commit_async+0x2f) [0xb771e4ff] -> dovecot/dict [0x804c930] -> dovecot/dict [0x804c35d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xe2) [0xb774a2d2] -> /usr/lib/d ovecot/libdovecot.so.0(io_loop_run+0x30) [0xb7749320] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xb7736dfa] -> dovecot/dict(main+0x19c) [0x804d00c] -> /lib/tls/i686/cmov/libc. so.6(__libc_start_main+0xe6) [0xb72dab56] -> dovecot/dict [0x804c051] Mar 27 11:45:51 ubuntu-test postfix/qmgr[2335]: 0F22B27F0D: removed Mar 27 11:45:51 ubuntu-test dovecot: lmtp(5262): read(/var/run/dovecot/dict) failed: Remote disconnected Mar 27 11:45:51 ubuntu-test dovecot: lmtp(5262): Disconnect from local: Client quit Thanks, e-frog ------------------------------------------------------------------------- # 2.0.beta4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-20-generic-pae i686 Ubuntu 9.10 auth_debug = yes auth_socket_path = /var/run/dovecot/auth-userdb auth_username_format = %Ln deliver_log_format = msgid=%m: from=%f: %$ dict { dictionary = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes namespace { hidden = no inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } namespace { location = virtual:/etc/dovecot/virtual:INDEX=~/.maildir/control prefix = virtual/ separator = / subscriptions = no type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { fts = squat fts_squat = partial=4 full=10 quota = dict:user::proxy::dictionary sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve-global/ sieve_dir = ~/.sieve } postmaster_address = postmaster@ubuntu-test protocols = imap lmtp managesieve quota_full_tempfail = yes sendmail_path = /usr/lib/sendmail service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0666 } } service dict { unix_listener dict { mode = 0666 } } service lmtp { unix_listener /var/spool/postfix/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve_deprecated { port = 2000 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol managesieve { mail_plugins = virtual } protocol lmtp { mail_plugins = virtual quota sieve } protocol lda { info_log_path = /var/log/deliver.log log_path = /var/log/deliver.log mail_plugins = virtual quota sieve } protocol imap { mail_plugins = quota imap_quota fts fts_squat virtual }

1 0

Re: [Dovecot] dovecot user
by Stan Hoeppner 27 Mar '10

27 Mar '10

Timo Sirainen put forth on 3/27/2010 2:18 AM: > On Sat, 2010-03-27 at 02:10 -0500, Stan Hoeppner wrote: >>> Maybe the native english speakers (and I'd think only a subset of them too). I had never heard of dovetail. >> >> I'm guessing that's because you're not a woodworker, or know any. ;) It's a >> great hobby if you ever found the spare time. > > Sure. But we're talking about UNIX admin kind people here. Somehow I > doubt they spent much attention to woodworking classes at school (we > actually had such classes, and I might know the Finnish word for > dovetail if someone told me it, but I doubt it's common knowledge in > either language). Probably depends on what city/state/province/country as well. I'm in the midwest USA, and alot of people in general, sysadmins or not, are DIY type folks. You grow up on a farm or in a small town and learn a whole lot of non computer stuff (including basic woodworking) before going to college and then to the big city for the sysadmin job. Then you visit mom/dad on the weekends, and they have you rebuilt the kitchen and bathroom. Then you decide to rebuild your own kitchen and bathroom. And then your neighbors find out you know how to do that kind of work and ... you lose a few more weekends. :( >>> I want something that's at least potentially understandable to people who understand english (and not just native speakers). I wouldn't know why some process is owned by user "dovel". That might not even make me realize it's a Dovecot process. >> >> How about "pigeon"? Dovecots house two kinds of birds, doves, and, far more >> often, pigeons. So, pigeon should be the new user name. No one knows what >> the heck a "dovecot" is until they look it up anyway (at least non Scots), >> so using "pigeon" is in keeping with naming your server Dovecot. There. >> Now that that's settled... > > But Dovecot is the name of the software, and admins know that, even if > they have no clue what it means. dove* as the username makes them think > of Dovecot regardless. You think anyone is going to add the user "pigeon" to any groups? I'm thinking that, as with "dovenull", that most would avoid touching "pigeon" at all costs. Then again, some may think their system was hacked, and want to remove the user "pigeon" lol. If your main goal is getting people to leave that user alone, I think pigeon would definitely fit the bill. And it adds a bit of humor to the mix since pigeons tend to crap all over everything. ;) >> dovecot dove-main >> dovecot-auth dove-auth >> imap-login dove-imaplgn >> pop3-login dove-poplgn >> imap dove-imap >> pop3 dove-pop3 >> >> Just a thought. But a nice thought at that. :) > > But you're talking about process names, right? That's already changed in > v2.0. You have one "dovecot" process and everything else is "dovecot/*". > For example: > > root 1840 0.0 0.0 43140 1328 pts/0 S+ 05:02 0:00 /usr/local/sbin/dovecot -F > dovecot 1841 0.0 0.0 30568 976 pts/0 S+ 05:02 0:00 dovecot/anvil > root 1842 0.0 0.0 30676 1120 pts/0 S+ 05:02 0:00 dovecot/log > root 2500 0.0 0.1 38524 2760 pts/0 S+ 08:59 0:00 dovecot/lmtp > root 2501 0.0 0.2 37684 4372 pts/0 S+ 08:59 0:00 dovecot/config > dovecot 2502 0.0 0.1 68500 3112 pts/0 S+ 08:59 0:00 dovecot/auth Ahh, sw333t! I haven't played with 2.0 yet so I hadn't seen this yet. That's precisely the kinda thing I had in mind. See? Great minds think alike. (most of the time anyway) ;) -- Stan

1 0

[Dovecot] dovecot user
by Stan Hoeppner 27 Mar '10

27 Mar '10

Sorry, meant this to go to the list. Timo Sirainen put forth on 3/27/2010 12:08 AM: > On 27.3.2010, at 6.49, Stan Hoeppner wrote: > >>> Tail just doesn't make much sense to me. Also it's not completely free >>> of pornographic associations either. :) >> >> No, no, totally free of pornographic connotation. Dovetail is a type of >> woodworking joint. That's what the vast majority of people on planet earth >> will associate "dovetail" with anyway. > > Maybe the native english speakers (and I'd think only a subset of them too). I had never heard of dovetail. I'm guessing that's because you're not a woodworker, or know any. ;) It's a great hobby if you ever found the spare time. >>> So my last idea: doveless. "It's less of a dovecot process." To me it >>> seems closer to perfect as anything I've seen so far. >> >> Or how about just "dovel", a crafty word smithing merge of dovecot+shovel? >> Although I'm unsure of any parallels between the work done by this thing and >> that performed by a shovel. ;) Still, it's catchy. > > I want something that's at least potentially understandable to people who understand english (and not just native speakers). I wouldn't know why some process is owned by user "dovel". That might not even make me realize it's a Dovecot process. How about "pigeon"? Dovecots house two kinds of birds, doves, and, far more often, pigeons. So, pigeon should be the new user name. No one knows what the heck a "dovecot" is until they look it up anyway (at least non Scots), so using "pigeon" is in keeping with naming your server Dovecot. There. Now that that's settled... Kinda related to the current subject, naming things, I personally believe renaming all of the processes with a "dove-" or similar at the start of the process name would be nice. I wish Wietse would do so with Postfix as well, although I've not mentioned it (yet). Something like this: dovecot dove-main dovecot-auth dove-auth imap-login dove-imaplgn pop3-login dove-poplgn imap dove-imap pop3 dove-pop3 Just a thought. But a nice thought at that. :) -- Stan

1 0

[Dovecot] corrupted mbox
by Jernej Porenta 27 Mar '10

27 Mar '10

Heya, we have two IMAP (UW-imap and dovecot) servers accessing the same mbox files for our users (don't ask why) and sometimes the UW-imap corrupts the mbox file. The mbox looks just like normal mbox except it does not have the proper 'From ' beginning of the file (usually there are some random tidbits in the begining of the file, which can be easily stripped to recover the working mbox). The problem is that if we use dovecot for POP3 server, the dovecot logs the mbox corruption just fine: POP3(username): Couldn't init INBOX: Mailbox isn't a valid mbox file But if we use IMAP for the same mailbox, dovecot opens the file and does not report any corruption, the user on the other hand sees just empty mailbox. So I was wondering if there are any possibilities to report mbox corruption with IMAP as well? thanks in advance, regards, Jernej

2 4

[Dovecot] shared mailboxes, mkdir_parents problem
by Leo Unglaub 27 Mar '10

27 Mar '10

Hi Friends, i have a little problem with my Dovecot installation. The normal installation works very well and now i have to configurate dovecot that all member from a domain can access all mailboxes from this domain. I configurate the shared namespace and set the IMAP ACL Flag but i can't abonement the other mailboxes. I get a error in the logs: > 2010-03-18 10:03:04 IMAP(unglaub): Info: maildir: > data=/var/mails/e-c-o.at/kirchmeir:INDEX=/var/mails/e-c-o.at/shared/mitarbeiter/kirchmeir > > 2010-03-18 10:03:04 IMAP(unglaub): Info: maildir++: > root=/var/mails/e-c-o.at/kirchmeir, > index=/var/mails/e-c-o.at/shared/mitarbeiter/kirchmeir, control=, > inbox=/var/mails/e-c-o.at/kirchmeir > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl: initializing backend > with data: vfile:/etc/dovecot-acl > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl: acl username = unglaub > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl: owner = 0 > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl vfile: Global ACL > directory: /etc/dovecot-acl > 2010-03-18 10:03:04 IMAP(unglaub): Info: acl vfile: file > /etc/dovecot-acl//.DEFAULT not found > 2010-03-18 10:03:04 IMAP(unglaub): Info: Namespace > shared/mitarbeiter/kirchmeir/: Permission lookup failed from > /var/mails/e-c-o.at/kirchmeir > 2010-03-18 10:03:04 IMAP(unglaub): Info: Namespace > shared/mitarbeiter/kirchmeir/: Using permissions from > /var/mails/e-c-o.at/kirchmeir: mode=0700 gid=-1 > 2010-03-18 10:03:04 IMAP(unglaub): Error: > mkdir_parents(/var/mails/e-c-o.at/kirchmeir) failed: Permission denied In this case the User unglaub(a)e-c-o.at try to access the mailbox kirchmeir(a)e-c-o.at. My config looks like this: > mail:~# dovecot -n > # 1.2.11: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.30-bpo.1-amd64 x86_64 Debian 5.0.4 ext3 > log_path: /var/log/dovecot/dovecot.log > log_timestamp: %Y-%m-%d %H:%M:%S > disable_plaintext_auth: no > login_dir: /var/run/dovecot/login > login_executable: /usr/lib/dovecot/imap-login > mail_privileged_group: mail > mail_uid: 501 > mail_gid: 501 > mail_location: maildir:/var/mail/%d/%n > mail_debug: yes > maildir_copy_preserve_filename: yes > mbox_write_locks: fcntl dotlock > mail_plugins: acl imap_acl > namespace: > type: private > separator: / > inbox: yes > list: yes > subscriptions: yes > namespace: > type: shared > separator: / > prefix: shared/mitarbeiter/%%n/ > location: maildir:/var/mails/e-c-o.at/%%n:INDEX=/tmp/%%n > list: children > lda: > postmaster_address: postmaster(a)e-c-o.at > mail_plugins: acl > auth_socket_path: /var/run/dovecot/auth-master > log_path: /var/log/dovecot/dovecot-deliver-errors.log > info_log_path: /var/log/dovecot/dovecot-deliver.log > auth default: > default_realm: e-c-o.at > passdb: > driver: ldap > args: /etc/dovecot/dovecot-ldap.conf > userdb: > driver: ldap > args: /etc/dovecot/dovecot-ldap.conf > socket: > type: listen > client: > path: /var/spool/postfix/private/auth > mode: 432 > user: postfix > group: postfix > master: > path: /var/run/dovecot/auth-master > mode: 384 > user: dovecot-data > group: dovecot-data > plugin: > acl: vfile:/etc/dovecot-acl > acl_shared_dict: file:/var/mail/%d/shared-mailboxes.db Do you have any idea why my setup isn't working correct? My users are stored in a LDAP (openLDAP) Server and the login works very well. For completion i post the LDAP-File to. > mail:~# grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf > hosts = 192.168.1.230 > dn = cn=ldapadmin,dc=e-c-o,dc=net > dnpass = xxxxxxxx > ldap_version = 3 > base = ou=smbUser,ou=dc,ou=at,dc=e-c-o,dc=net > scope = subtree > user_filter = (&(objectClass=posixAccount)(uid=%n)) > user_attrs = mail=mail > pass_filter = (&(objectClass=posixAccount)(uid=%n)) > pass_attrs = uid=user,userPassword=password,\ > homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid > default_pass_scheme = CRYPT Thank you very much. Greetings from Austria Leo

4 3

[Dovecot] mail_save_crlf Semantics
by Sabahattin Gucukoglu 27 Mar '10

27 Mar '10

Hi, It's not clear from the configuration when CR/LF conversion happens with mail_save_crlf set. Does this only happen with appends, or do all mails handled by Dovecot always get converted when opened? Cheers, Sabahattin

2 1

[Dovecot] 2.0.beta4 compile errors
by Steven King 27 Mar '10

27 Mar '10

I am unable to get 2.0.beta4 to compile. I get the following errors: /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../lib64/libwrap.a(hosts_access.o): In function `host_match': hosts_access.c:(.text+0x625): undefined reference to `yp_get_default_domain' collect2: ld returned 1 exit status make[3]: *** [tcpwrap] Error 1 make[3]: Leaving directory `/root/dovecot/dovecot-2.0.beta4/src/util' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot/dovecot-2.0.beta4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot/dovecot-2.0.beta4' make: *** [all] Error 2 Any help would be appreciated. -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional

2 1

[Dovecot] dovecot 2.0beta4 zlib
by Renaud Allard 27 Mar '10

27 Mar '10

Hello, When trying to enable the zlib and imap_zlib plugins, I get the following error: imap: dovecot/imap:/opt/dovecot/lib/dovecot/lib2 0_zlib_plugin.so: undefined symbol 'i_stream_create_bz2' I did not compile it using --with-bzlib though and bz2 libs are available on the system. Best Regards

2 1

[Dovecot] cmusieve auto-reply and quota
by Mauro Faccenda 27 Mar '10

27 Mar '10

Hi there, I'm quite new to Dovecot, but already can tell that it is a really great work, congrats to the developers! But I'm having a little problem and couldn't figure it out how to solve. First, let me talk about my setup: I'm running Debian 5 (Lenny) with it's default Dovecot (common, pop3 and imap) packages (version 1:1.0.15-2.3+lenny1), I really would like to keep it this way unless I haven't another option. All authentication is made through a MS Active Directory and messages delivered to a virtual mailbox (/var/vmail/<domain>/<mailbox>), using Postfix as SMTP, that uses procmail (just for filtering the messages, not to deliver) that calls Dovecot's deliver like this: -- :0 w | $DELIVER -d $RECIPIENT -e -- $DELIVER points to /usr/lib/dovecot/deliver and $RECIPIENT is fed by Postfix in it's master.cf All this work great. Then I needed to enable quotas it's working as well. Here is the section that show how I've set it up: -- protocol lda { mail_plugin_dir = /usr/lib/dovecot/modules/lda mail_plugins = cmusieve quota postmaster_address = postmaster(a)do.ma.in hostname = mybox.do.ma.in auth_socket_path = /var/run/dovecot/auth-master quota_full_tempfail = no } -- I also want to run some sieve scripts just to be able to do some auto-replies (i.e. Out of office), and also it works well. Here is an example of a sieve I was using in some tests: -- require ["fileinto", "vacation"]; if header :contains "X-DSPAM-Result" "Spam" { stop; } vacation :days 1 :subject "Out of office reply" :addresses ["john.doe(a)do.ma.in", "jd(a)do.ma.in"] "I'm out of office, please contact Joan Doe instead. Best regards John Doe"; -- And as I said it works. But when I send a message to this mailbox that could exceed it's quota I get this on my logs: -- Mar 25 14:02:25 mybox postfix/pickup[21407]: 68D1DA82F: uid=103 from=<> Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)other.do.ma.in>: sent vacation response to <faccenda(a)other.do.ma.in> Mar 25 14:02:25 mybox postfix/cleanup[22119]: 68D1DA82F: message-id=<dovecot-1269536545-332912-0(a)do.ma.in> Mar 25 14:02:25 mybox postfix/qmgr[17299]: 68D1DA82F: from=<>, size=623, nrcpt=1 (queue active) Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)other.do.ma.in>: save failed to INBOX: Quota exceeded Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): sieve runtime error: Keep: Generic Error Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): sieve_execute_bytecode(/var/vmail/do.ma.in/john.doe/.dovecot.sievec) failed Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)do.ma.in>: Rejected: Quota exceeded Mar 25 14:02:25 mybox postfix/pipe[22086]: 7C666A825: to=<john.doe(a)do.ma.in>, relay=procmail, delay=1.1, delays=0.39/0/0/0.68, dsn=4.3.0, status=deferred (temporary failure) -- And every time the server tries again to deliver that message it re-sends the auto-reply. Is it an undesirable behavior, isn't it? Does anyone knows how to address it? Also, I thought that that configuration (using the -e parameter to deliver) and the "quota_full_tempfail = yes" would make give an permanent error, not trying to deliver that message again. What is wrong about it? Thanks in advance,

2 1

[Dovecot] A questions about consume_results (driver-pgsql.c)
by Rainer Weikusat 27 Mar '10

27 Mar '10

Code -------------- static void consume_results(struct pgsql_db *db) { do { if (!PQconsumeInput(db->pg)) break; if (PQisBusy(db->pg)) return; } while (PQgetResult(db->pg) != NULL); if (PQstatus(db->pg) == CONNECTION_BAD) io_remove_closed(&db->io); else io_remove(&db->io); db->querying = FALSE; if (db->queue != NULL && db->connected) queue_send_next(db); } --------------- This is the only part of the driver-pgsql.c code where a CONNECTION_BAD does not result in driver_pgsql_close being called. This will likely happen after the next query (from queue or a new one) failed because the connection was bad. Is there a reason for this?

2 2

[Dovecot] v2.0.beta4 released
by Timo Sirainen 27 Mar '10

27 Mar '10

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for a couple of weeks. Major changes since beta3: - auth process now runs as $dovecot_internal_user ("dovecot") by default. Auth worker processes still run as root by default, so this won't break PAM etc, but it could break passwd-file configurations. - It can now read v1.2's dovecot.conf file. If you find that it won't read your config, let me know and I'll see about adding code to fix it. It'll log warnings about each obsolete setting it sees. The easiest way to get rid of the warnings is to just translate your old config to v2.0: doveconf -n -c old.conf > new.conf - auth passdb/userdb configuration in example-config is now a bit different .. hopefully less confusing to new people than the old one. - added support for auth settings (including passdb/userdb) inside protocol sections, so it'll affect only those protocols - mail_plugins can now be set more easily. you can have a single global mail_plugins and then add more plugins to it like protocol imap { mail_plugins = $mail_plugins imap_quota } - doveconf finally shows all settings, including all protocol, local and remote sections - doveadm quota get|recalc command added. This is a plugin (yeah, doveadm now supports plugins!), so you must have a global mail_plugins=quota setting for the command to show up. - doveadm kick user/network to kick out logged in users (by sending TERM signal to processes). This was written by Pascal Volk. - and of course tons and tons of fixes all around

6 11

[Dovecot] dovecot 2.0 fails self-tests
by Michal Hlavinka 27 Mar '10

27 Mar '10

Hi, is it expected that dovecot 2.0.beta4 pass all of it's self-tests or some failures are normal? I've tried make check and everything passed up to this test: ... message_date_parse(7) ................................................ : ok 0 / 8 tests failed test-message-decoder.c:67: Assert failed: message_decoder_decode_next_block(ctx, &input, &output) test-message-decoder.c:78: Assert failed: output.size == 3 test-message-decoder.c:84: Assert failed: output.size == 14 test-message-decoder.c:85: Assert failed: memcmp(output.data, " bar", 14) == 0 message decoder ...................................................... : FAILED 1 / 1 tests failed Regards, Michal Hlavinka

2 3

[Dovecot] CentOS yum update causing died unexpectedly
by dovecot＠corwyn.net 26 Mar '10

26 Mar '10

Running CentOS 5.x running a postfix/dovecot implementation. Dovecot 1.1.8. I just ran a full system update in my dev environment, and now I'm occasionally getting: Mar 26 07:15:43 example dovecot: auth(default): worker-server(test222(a)int.example.com,127.0.0.1): Aborted: Worker process died unexpectedly in /var/log/maillog. Any suggestions on where to look to figure out what's causing this? I don't see that error at all in the past 4 weeks of logs in production. Thanks Rick Rick Steeves http://www.sinister.net In reality nothing is more damaging to the adventurous spirit within a man than a secure future - Alexander Supertramp

2 1