- dovecot - dovecot.org

[Dovecot] Missing public folder
by komodo 16 Nov '11

16 Nov '11

Hi i am using dovecot 2.0.13 and i can't see public folder in my mail client. But what is strange, it was working after instalation, and i don't know when it dissapeared. Maybe after some upgrade ? When i enable debug, then i can see in my log that folder exists and no errors. Please where should i find the problem ? Thanks Martin Here is log Nov 7 11:00:27 OVZ dovecot: imap(komodo): Debug: Namespace : type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Nov 7 11:00:27 OVZ dovecot: imap(komodo): Debug: maildir++: root=/home/komodo/Maildir, index=, control=, inbox=/home/komodo/Maildir Nov 7 11:00:27 OVZ dovecot: imap(komodo): Debug: Namespace : type=public, prefix=spam_learner., sep=., inbox=no, hidden=no, list=yes, subscriptions=no location=maildir:/home/shared/Maildir Nov 7 11:00:27 OVZ dovecot: imap(komodo): Debug: maildir++: root=/home/shared/Maildir, index=, control=, inbox= Here is my conf # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab037.1 x86_64 CentOS release 5.5 (Final) default_client_limit = 1300 disable_plaintext_auth = no hostname = somehost.com mail_location = maildir:~/Maildir 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 mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } namespace { location = maildir:/home/shared/Maildir prefix = spam_learner. separator = . subscriptions = no type = public } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.d/ sieve_dir = ~/sieve } protocols = imap pop3 sieve sendmail_path = /usr/sbin/sendmail.exim service imap-login { process_limit = 1000 process_min_avail = 30 } ssl_cert = </etc/pki/dovecot/certs/host.pem ssl_key = </etc/pki/dovecot/private/host.pem userdb { driver = prefetch } protocol lda { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 100 }

2 1

Re: [Dovecot] Please advise on very fast search
by Stan Hoeppner 16 Nov '11

16 Nov '11

On 11/16/2011 12:15 AM, Alexander Chekalin wrote: > Hello, Stan, > >> This is why I recommended mbox in the first place. If your only writes >> to these mailbox files are appends of new messages, mbox is the best >> format by far. It's faster at appending than any other format, and it's >> faster for searching than any other. > > I now seriously consider to use mdbox due to its nice self-regulation. > After all it I believe mdbox should do file compression on its own, no > cron scripts required. mbox and mdbox each has strengths and weaknesses. mbox will compress with a higher ratio than mdbox. You already have a nightly script that moves all mail from the day into a new file. Piping that through gzip or bzip2 is a no brainer. It'll add one line to your existing script, if that. Dovecot will decompress the file transparently when you access it via IMAP. And again since it's a single file searching it is much faster. With mbox you will have a single file for each day of emails. This seems ideal for archive purposes, one file per day. mdbox does fully transparent de/compression which is nice. The downside is that Dovecot does dbox compression on a per email basis, not a per file basis. So your compression ratio will be much less than with mbox, especially with bzip2 which works best on files over 900KB in size. Most emails are less than 8KB. Using mdbox will yield multiple files per day of emails instead of just one. Either format is much better than maildir for archiving. >> It's an archive. You're not going to use maildir so you don't need >> random IOPS performance. Thus RAID5/6 are a much better fit for an >> archive as you get better read performance, with more than adequate >> write performance, and you use less disks. And as this is an archive, >> you don't need real time automatic/transparent compression. Thus I >> recommend something like: >> >> 1. Debian 6 w/linux-image-2.6.39-bpo.2-amd64 or a custom rolled >> 2.6.39 or later kernel >> 2. hardware RAID5 w/large (2TB) SATA disks, 512B native sectors >> e.g. MegaRAID SAS 9261-8i, 4 Seagate Constellation ES ST2000NM0011 >> Specify a strip size of 256KB for the array >> Perma set /sys/block/sdX/read_ahead_kb to 512 so you're reading >> ahead 1024 sectors at a time instead of the default of 256. This >> will speed up your searches quite a bit. >> 3. XFS filesystem on the RAID device, created with mkfs.xfs defaults >> 4. mbox w/zlib plugin. Compress daily files each night with a script >> 5. You don't need LVM with a good RAID card (or with mdraid). This >> controller can expand the RAID5 up to 8 drives (up to 32 drives max >> using SAS expanders) > > We are considering to get HP DL180G6 server for 8 or 14 drives bays The P410 tops out at 8 drives, so get the 8 drive model. Start with 4 x 2TB drives in RAID5. Add 4 more drives when you need the capacity, and when drive prices are back down to normal (see below). http://h18004.www1.hp.com/products/quickspecs/13248_na/13248_na.html > (base model price is somewhat equal, but additional drives adds up cost) Especially right now in 2011. Flooding in Thailand, where 25% of the world's drives are produced, has doubled the cost of all hard drives worldwide. Now is a horrible time to buy spinning drives. I've read it may be 12 months before prices start coming back down... > with HP Smart Array P410 RAID controller (some servers are equipped with > this controller by default) with 256 Mb battery-backed cache, but I'll > check your suggestions! The P410 should be fine for a dedicated archive server. > What memory size should I plan in the server? You're talking about AMD64 > OS image, and 64-bit software are like to consume more memory that > 32-bit, so looks like your talking about pretty huge RAM, and I don't > believe it's necessary, or maybe I'm wrong? The memory footprint of 64bit binaries is nothing to worry about. The additional amount consumed is more than offset by the performance gained with direct access to RAM above 4GB compared to the performance of PAE. Keep in mind that 90% of your memory will be eaten by Linux buffer cache. Your binaries will account for less than 5% of your RAM consumption. If I understand correctly how you will use this archive server, then 8GB should be plenty. 8GB is standard on the 8 drive DL180 G6. http://h18004.www1.hp.com/products/quickspecs/13248_na/13248_na.html > Problem is I have no experience with XFS and not sure I can tune it in > the best way, so I'll go with mkfs.xfs defaults, I think. With only 4 drives and using a P410 w/cache and RAID5, doing manual XFS tuning isn't necessary for good performance, especially for an archive application which is data heavy, not metadata heavy. Setting sunit/swidth to match the RAID5 layout may increase performance slightly due to stripe aligned writes, but not enough that I'd worry about it. Just use the mkfs.xfs defaults. If you get the BBWC for the P410, enable the controller write cache, and mount XFS with 'nobarrier'. This will increase write performance quite a bit as fsyncs will complete instantly. > Hope we'll see Dovecot 2.1.x stable soon, as I'd like to use fts plugins > and 2.1 handle that much better, but I don't like the idea of use > unstable in production. Me neither. Speaking of archive/search, did you take look at Enkive yet? http://www.enkive.org/ > Thank you for taking your time on my case, You're welcome Alexander. -- Stan P.S. You may wish to implement dnswl.org ;)

1 0

[Dovecot] Chroot
by Bambero 16 Nov '11

16 Nov '11

Hello, I have successfully setup dovecot with chroot but there are two things yet 1. submission_host problem (I posted message 2 days ago) 2. Problem with acl's and sharing: all maildirs are located in: /var/mail/jdoe(a)example.com/Maildir so: mail_chroot=/var/mail I setup acls with: 10-mail.conf ... namespace { type = private separator = / prefix =. inbox = yes hidden = no list = yes subscriptions = yes } namespace { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u subscriptions = yes list = yes } ... 90-acl.conf ... plugin { acl = vfile:cache_secs=5 } plugin { acl_shared_dict = file:/%i.db } ... Setting acl is no problem there are dovecot-acl dovecot-acl-list in Maildir. and dictionary /var/mail/xxx.db contains list od shares I can also see shared folder in my IMAP client but when trying to subscribe i got error: Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No such file or directory Error: Namespace 'shared/': Could not lookup home for user jdoe(a)example.com /var/dovecot/auth-userdb is not accessible because chroot. But why userdb is necessary in this case ? I hope there is a solution without disabling chroot. Below my basic configuration. Regards, Bambero # 2.0.13: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.0 i386 auth_mechanisms = plain login digest-md5 cram-md5 apop default_internal_user = _dovecot default_login_user = _dovenull first_valid_gid = 1000 first_valid_uid = 1000 last_valid_gid = 10000 last_valid_uid = 10000 mail_chroot = /var/mail mail_location = maildir:~/Maildir 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 imapflags notify mbox_write_locks = fcntl mmap_disable = yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { autocreate = Trash autocreate2 = Spam autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Sent autosubscribe4 = Drafts quota = maildir:User quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_global_path = /etc/sieve/default.sieve } protocols = imap pop3 sieve sieve service auth { unix_listener auth-client { mode = 0660 user = _exim } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_ca = /etc/ssl/ca-bundle.crt ssl_cert = </etc/ssl/mycert.crt ssl_key = </etc/ssl/private/mycert.key submission_host = 127.0.0.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } valid_chroot_dirs = /var/mail protocol lda { mail_plugins = sieve quota autocreate } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_plugins = quota imap_quota autocreate } protocol pop3 { mail_plugins = quota imap_quota autocreate pop3_client_workarounds = outlook-no-nuls oe-ns-eoh }

2 5

[Dovecot] How to do SEARCH with doveadm
by Alexander Chekalin 16 Nov '11

16 Nov '11

Hello, I'm still playing with search messages from/to specified email address. In fact I need to do that to take such messages and copy it to another mailbox (so that box will contain 'Search results' and will be available to examine by any IMAP client). I've put my mailings in mdbox storage format, and use latest 2.1 beta version of Dovecot to be sure I use the freshest approach in search (and plan to use Solr FTS as well). The setup is each, I use passdb { driver = passwd-file args = /etc/dovecot/auth/%Lu } and userdb { driver = static args = uid=dovecot gid=dovecot home=/MAIL/mail_storage/%Lu } and put user:password pair in file named after my mailbox in /etc/dovecot/auth/ (let's name it test(a)domain.com) and the messages are at /MAIL/mail_storage/test(a)domain.com/... While I use it from IMAP client it works nicely. Ok, I put somewhat 5800 messages in INBOX, and IMAP pretty fast in working with it. But as I try to use doveadm to search for messages I need I simple lost my way (doing it under root): # doveadm search ALL doveadm(root): Error: chdir(/root/) failed: Permission denied (euid=104(dovecot) egid=106(dovecot) missing +x perm: /root, dir owned by 0:0 mode=0700) doveadm(root): Error: chdir(/root) failed: Permission denied Whatever cli command I try doveadv try to find messages in /root dispute it is at /MAIL/mail_storage/%Lu. How can I make doveadv use right mail path? In fact, I don't want to use system users to work with mail, it'll be simple virtual mail user, so it is pointless to set up special system user to do that search. I think I lost myself in general concept of how Dovecot handles users and credentials, so please please please push me in right direction! Thank you, Alexander

1 0

[Dovecot] Creating a password_scheme
by Jordi Llonch 16 Nov '11

16 Nov '11

Hello, I am trying to develop a password_scheme for the Django passwords. After building and installing the module in $module_dir/auth/password/djangopass.so, also tried libdjangopass.so and libdjangopass_plugin.so, Dovecot does not recognize the scheme: doveadm pw -l CRYPT MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN CLEARTEXT CRAM-MD5 HMAC-MD5 DIGEST-MD5 PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY RPA SHA256-CRYPT SHA512-CRYPT Please can you help me? Thanks -- Jordi Llonch # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.40.3-0.fc15.x86_64 x86_64 Fedora release 15 (Lovelock) ext4 ----------password-scheme-django.c-------------------------- #include <stdio.h> #include <ctype.h> #include <stdlib.h> #include <string.h> #include <dovecot/lib.h> #include <dovecot/hex-binary.h> #include <dovecot/password-scheme.h> #define uchar unsigned char static bool djangopass_verify(const char *plaintext, const char *user, const unsigned char *raw_password, size_t size) { return TRUE; } void djangopass_generate(const char *plaintext, const char *user, const unsigned char **raw_password_r, size_t *size_r) { } struct password_scheme djangopass_scheme = { "DJANGO", PW_ENCODING_BASE64, 0, djangopass_verify, djangopass_generate }; struct module; void djangopass_init(struct module *module) { password_scheme_register(&djangopass_scheme); } void djangopass_deinit(void) { password_scheme_unregister(&djangopass_scheme); } ---------------------------------------------------------------------------

2 1

[Dovecot] setting namespaces using script-login environment in 2.0
by Alexander 'Leo' Bergolth 16 Nov '11

16 Nov '11

Hi! With dovecot 1.x, I was using a post-login script to dynamically add shared mailboxes using NAMESPACE_X.. environment variables, based on filesystem permissions: After login, the post-login script was executed with user permissions (mail_drop_priv_before_exec=yes). It added all subdirectories of "/var/spool/mail/Shared" as namespaces for which the user had write permissions. E.g.: NAMESPACE_2='maildir:/var/mail/Shared/spamrep:INDEX=~/Maildir/index/Shared/spamrep' NAMESPACE_2_PREFIX=Shared/spamrep/ NAMESPACE_2_SEP=/ NAMESPACE_2_TYPE=public NAMESPACE_2_LIST=yes See the attached post-pogin-script for details. After switching to 2.0.14 (using executable script-login -d...), the script actually gets executed but the namespace settings do not seem to be honored. Besides, I don't see any pre-set NAMESPACE_ environment variables anymore. Have environment based namespace settings been abandoned in 2.0? Does Dovecot 2.0 maybe provide a better way to only display those folders, for which the user has at least read permissions? (Unix-permission based) Thanks in advance, --leo -- e-mail ::: Leo.Bergolth (at) wu.ac.at fax ::: +43-1-31336-906050 location ::: IT-Services | Vienna University of Economics | Austria

3 5

[Dovecot] Usage of director without LMTP
by Oliver Eales 16 Nov '11

16 Nov '11

Hello, we want to migrate our dovecot 1.2 installation to verison 2.0 and want to use the director feature of version 2. Currently we have a two tier archtiecture, with dovecot proxys and a mailstore togehter with indexes on NFS. (With the common problems of this setup...) For the final setup we want to utilize the director for all protocols (IMAP,POP,LMTP,SIEVE). During the transition phase we will not be able to use LMTP for mail delivery, but we are still stuck with deliver as LDA. So for mail delivery we will not have the fixed user/server assignment, but rather a random assignment. What NFS- and locking settings should be used on the backend servers in this case. And should i use different settings for the host the deliver is executed than the IMAP/POP3 hosts which are accessed through a director proxy. Thanks in advance, Oliver Eales

2 1

[Dovecot] Invalid "doveadm search" queries not rejected
by Peter Williams 16 Nov '11

16 Nov '11

Hello, I think I've encountered a bug in Dovecot 2.0.9 (as provided on CentOS 6). According to the doveadm-search-query(7) manual page, a "mailbox" specification can only come at the beginning of a search query. However, if I put a mailbox specification in the middle of a query, not only do I not get an error message, I get surprising results: $ doveadm search mailbox A |wc -l 6979 $ doveadm search mailbox B |wc -l 206 $ doveadm search mailbox A OR mailbox B |wc -l 42492 If it became possible to do boolean logic on mailbox queries, that'd be cool. But barring that, these invalid queries should be rejected. Relatedly, if I can only do simple mailbox filtering, does anyone know of a clever way to efficiently emulate more complex boolean logic? Please CC me on any replies as I'm not subscribed to the list. Thanks, Peter -- Peter Williams / peter(a)newton.cx

2 2

[Dovecot] Deleting a mailbox and all its children
by Micah Anderson 16 Nov '11

16 Nov '11

I'm looking at scripting a mechanism to delete a mailbox, which is easy with 'doveadm mailbox delete' -- however it gets complicated when there are children of arbitrary depth, for example, I may have this: restored.daily1.INBOX restored.daily1.Sent restored.daily1.Mystuff restored.daily1.Mystuff.foo I would like to delete the 'restored' mailbox and all its children (and unsubscribe the folders), but the 'doveadm mailbox delete' command wont delete any children. I'm surprised that there isn't a -r (recursive) option to 'doveadm mailbox delete', but perhaps I am missing the easier way to handle this? thanks for any ideas or suggestions! micah --

3 2

[Dovecot] Excessive imap-logins, never die
by Nick Edwards 16 Nov '11

16 Nov '11

Hiya, Today I note there are 38 imap-logins that seem to be stale on our staff imap server, they do not seem to die off, new imap-logins are created with new logins and exit accordingly. Now, these are from our monitoring software that runs on another server on our LAN. Our corporate link was taken down for 2 hours for urgent relocation of fibre (demolishing old adjoining building, and just in case, they needed to move it which we were glad about), so, this begs the question, why would imap-logins be there I guess in some sort of wait state, even with a still working internal DNS (internal view as well) the only difference is no actual internet connection in this time. A week ago when they first started to working and we lost internet for 45 minutes I also saw a few extra stale imap-logins, but after todays events, I decided this is a bigger issue that needs to be looked into, as dovecot required a restart to clear it all (I wasnt going to sit there killing individual PIDs all evening). Dovecot version 1.2.17, built from source

2 2