- dovecot - dovecot.org

[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