- dovecot - dovecot.org

[Dovecot] Warning about NFS but using local fs for INDEX
by Herbert Gasiorowski 12 Jun '07

12 Jun '07

I am playing around with dovecot and want to use local filesystem for indexing. But whenever I open a new imap connection the following warning is shown: Apr 30 10:14:42 beira dovecot: Mailbox indexes in /app/home/gasi are in NFS mount. You must set mmap_disable=yes to avoid index corruptions. If you're sure this check was wrong, set nfs_check=no. /app/home is a NFS mounted filesystem, but I want dovecot to use /export/dovecot/gasi for indexing (See namespaces below). I shurely can follow the hints(nfs_check=no), but I am not shure if I did something wrong or maybe someday will change the configuration and forget to enable the nfs check. dovecot version: dovecot-1.0-1.2.rc15.el5 on CentOS 5.0 (with all updates). [root@beira etc]# dovecot -n # /etc/dovecot.conf syslog_facility: local6 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 namespace: type: private separator: / location: mbox:~/Mail:INBOX=/var/spool/mail/%u:INDEX=/export/dovecot/%u inbox: yes namespace: type: private separator: / prefix: #home-tmp/ location: mbox:~:INDEX=/export/dovecot/%u auth default: passdb: driver: pam args: imap userdb: driver: passwd

2 2

[Dovecot] error in logfile
by Luigi Rosa 12 Jun '07

12 Jun '07

With Dovecot 1.0.0: May 11 12:16:35 mail dovecot: IMAP(xxx): stat(/var/spool/mail2/xxx/.Trash.Squid-it/new) failed: No such file or directory With Thunderbird 2.0 IMAP client: * user deleted the mailbox * TB moved the mailbox to Trash * user asked TB to empty Trash * the above message appeared No warning/error was reported bt TB to user. I don't think it's an error and should not be logged. Ciao, luigi -- / +--[Luigi Rosa]-- \ You can tune a radio, but you can't tuna fish.

2 1

[Dovecot] Getting rid of the common newbie problems
by Timo Sirainen 12 Jun '07

12 Jun '07

I think the most common Dovecot newbie problems are: - Not looking at the (correct) logs for errors - Authentication problems - Mail location problems - Mail permission problems Below are some of my ideas how I could stop people from asking these questions with future Dovecot (v1.1+) releases. Suggestions welcome. Distribution people especially should say if they're against some change. * Logging The log file problem is the most annoying one, because a lot of the other problems can be solved once the admin figures out that Dovecot is actually giving useful error messages. Often the admin is only looking at the log file where "info" messages go (eg mail.log) because Dovecot logs its startup message and login messages there, but not where the errors go (eg mail.err). This has happened even with people who in general are experienced sysadmins. Logging to eg. /var/log/dovecot.log by default would be helpful here, but it's probably better to log via syslog by default. Cyrus logs to "local6" by default. Perhaps for Dovecot v1.1 I should make that the default too? Looks like in my Debian system the info messages then go to both /var/log/messages and /var/log/syslog. Error messages only go to /var/log/syslog. So there still isn't by default a single log file where the errors are logged, but it might help a bit. * Authentication Authentication problems can usually be solved by telling the user to set auth_debug_passwords=yes and looking at the logs. I'm not sure if there's anything that can be helped in here. Except the logging message could be updated a bit: "Aborted login: user=<asdga>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, 1 failed authentications" So the last "n failed authentications" could be added, where n could also be 0. Another possibility would be to make Dovecot remember if there have been any successful logins (/var/lib/dovecot/success file) and if not, give a bit more helpful error messages: - Client gets: "NO Authentication failed. Refer to server log for more information." instead of the normal "NO Authentication failed." - Log contains: "Aborted login: user=<asdga>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, 1 failed authentications (set auth_debug_passwords=yes to debug the problem)" I'm not sure if this is a good idea. * Mail location It seems to be difficult for some people to set mail_location. I don't know if anything can be done before Dovecot v2.0 where I'll split it to multiple settings, such as: driver = maildir root_dir = ~/Maildir index_dir = /var/indexes/%u Another problem that seems to be difficult to understand is why the mail directory contains "HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB". The whole userdb concept appears to be weird. This could anyway be fixed by giving an error message earlier and failing the login with internal error. Probably the best place to give the error message would be already in the userdb lookup in dovecot-auth, but that would require that doveoct-auth knows if the home directory is really needed, and to give a useful error message it would also need to tell where it's tried to be used (mail_location, or some namespace's location, or ..). Probably too much trouble to be worth it. So the next best thing is to give the error when it's used: "Home directory is used in mail_location, but userdb didn't return a home directory" It would be nice if it didn't say userdb, but rather the userdb's name. I guess that would be possible if dovecot-auth told master (or deliver) which userdb was used, but that would normally be just extra overhead. * Mail permissions If mail location is difficult for some, then the concept of UIDs are how they're used in Dovecot is pretty much impossible for some to understand. One of the problems is that there exists "dovecot" user. So people think that their mails should be owned by the dovecot user. Although I've mentioned in everywhere I can think of that this should not be done, it won't help because either people won't read the pages or even if they do, they somehow still fail to ignore it even though it's written in bold. So unless people (and most importantly, distributions) are against it, I think the "dovecot" user should be renamed. "dovelogin" perhaps. In future I might split dovecot-auth even more, and then I would like to create a "doveauth" user as well. Another possibility would be to drop the dovecot user completely and instead use "nobody". That would mean that other nobody processes could kill Dovecot's login processes, but that's pretty much it. Once people understand that "dovecot" isn't the right user, they hit the next problem: "How do I tell Dovecot to run as vmail user?" I can paste links to wiki pages or tell them to "make userdb return uid=vmail", but that just doesn't seem to get through. There needs to be an easier way, and I think I figured out what it is: Add new "mail_uid" and "mail_gid" settings to dovecot.conf. Deprecate user_global_uid/gid in dovecot-ldap.conf and make all the userdbs mention that the uid/gid returned by userdb can be used to override the global mail_uid/gid. Perhaps also add "mail_home" template. This change makes it unnecessary to have a userdb configured at all. - "How do I tell Dovecot to run as vmail user?" - "Set mail_uid = vmail" in dovecot.conf - "Thanks"

10 36

[Dovecot] Dovecot LDA and address extensions
by Tom Metro 12 Jun '07

12 Jun '07

I'm converting over a virtual user installation that used Postfix and maildrop with a MySQL back-end for mailbox lookups to use Dovecot LDA. The maildrop setup used a database table like: +-------------------------+--------+-------------+--------------------+ | address | owner | domain | mailbox | +-------------------------+--------+-------------+--------------------+ | postmaster(a)example.com | tmetro | example.com | .admin.postmaster/ | | root(a)example.com | tmetro | example.com | .admin.root.lex/ | | tmetro(a)example.com | tmetro | example.com | .INBOX/ | | tmetro+spam(a)example.com | tmetro | example.com | .spam.tmetro/ | [...] where maildrop was handed ${recipient} from postfix, and it queries the above table matching ${recipient} to the address column, getting back the expression CONCAT_WS('/','/var/mail',domain,owner) as the home directory, and CONCAT_WS('/','/var/mail',domain,owner,mailbox) as the mailbox. The UID/GID are fixed, as this is a virtual user setup. So looking up the mailbox for the user postmaster(a)example.com returns: /var/mail/example.com/tmetro/.admin.postmaster/ Currently I'm using a static user database with Dovecot. This SQL appears to replicate the maildrop setup: user_query = SELECT CONCAT_WS('/','/var/mail',domain,owner) as home, CONCAT_WS('/','maildir:/var/mail',domain,owner,mailbox) as mail, 5000 as uid, 5000 as gid FROM vmbx2 WHERE userid = '%u' And this works for mail deliveries. The problem with this is that not only is a database lookup overkill for the IMAP server, as the root mail location for IMAP users follows a simple pattern adequately represented by the static userdb, it also breaks IMAP, because the returned 'mail' overrides mail_location, (currently set to maildir:/var/mail/%d/%n/), so for user tmetro(a)example.com it returns: maildir:/var/mail/example.com/tmetro/.INBOX/ instead of: maildir:/var/mail/example.com/tmetro/ (which is the same as the home directory). Can the "userdb sql" directive be added to the "protocol lda" section? Or perhaps instead create a new "auth lda" section, and move the "userdb sql" and "socket listen" directives to that section? The second issue is how to best deal with address extensions, something that wasn't fully implemented in the maildrop setup. Ideally I'd like a setup where a lookup is first performed for user+ext@domain, and if it fails to return a mailbox, then lookup user@domain. Assuming Dovecot can handle a multi-row query result (grabbing the first record and ignoring the rest), this can probably be hacked using an appropriate WHERE expression. But the difficulty is getting the address components. Postfix will provide them, but Dovecot's deliver doesn't seem to have a way of receiving them and passing them on to the user query. The example LDA setup shown here: http://wiki.dovecot.org/LDA/Postfix suggests passing the extension as an argument to the mailbox (-m) switch. But this assumes that one wants a one-to-one direct mapping between extensions and mailbox names. I suppose I could switch from: -d ${user}@${nexthop} to: -d ${recipient} and add even more complexity to the SQL to parse out the extension. But I'd rather avoid embedding the extension separator character in the SQL, and would rather eliminate it from the database as well. Maybe Sieve is the answer. I presume the argument to -m could be inspected in a Sieve script, which could then map to the desired target mailbox. The non-IMAP users (like postmaster(a)example.com) could be reimplemented as aliases that redirect to a user+ext(a)example.com address for the user responsible for that domain. But using Sieve scripts for extension to mailbox mappings seems far less elegant than using a database. Maybe I need to wedge a wrapper program between Postfix and deliver that will accept the address components from postfix, perform the lookup, and convert the results into a -d argument pointing to the "owner" (see table above) and a -m argument pointing to the mailbox. On a side note... When I used this command in postfix's master.cf: /usr/lib/dovecot/deliver -d ${user}@${nexthop} -n -m ${extension} as recommended in the wiki, the following error gets logged: ... status=bounced (command line usage error. Command output: Fatal: Unknown argument: -d Usage: deliver [-c <config file>] [-d <destination user>] [-m <mailbox>] [-f <envelope sender>] ) which doesn't make a lot of sense. I suspect what it is trying to say is that it didn't like something about the argument to the -d switch. Maybe that should be ${domain} instead of ${nexthop}. (What's up with all the whitespace between "[-m <mailbox>]" and "[-f <envelope sender>]"? Also, might be a good idea to have deliver always write errors - even startup errors - to the specified logging facility, given that not all programs that launch it will report what it writes to STDERR. I notice most postfix commands - even the ones people interact with - log errors.) I ended up switching to -d ${recipient} to emulate the old maildrop setup for now, and that worked fine. The sample dovecot.conf has: ## dovecot-lda specific settings ## # socket listen { # master { # path = /var/run/dovecot/auth-master I uncommented the first two lines, but left the 'path' directive commented, under the assumption that the comment was showing the default. But without it uncommented, the socket doesn't get created. This is an inconsistency compared to how defaults are shown elsewhere in dovecot.conf. -Tom

2 1

[Dovecot] vpopmail quota
by Onno Molenkamp 12 Jun '07

12 Jun '07

Hi, I'd like the vpopmail user database to return the quota settings for users, instead of having to rely on the validity of the maildirsize files. It doesn't look like this is currently possible. Would simply adding a auth_stream_reply_add call for "quota" with a suitable value in vpopmail_lookup be sufficient to make this work? (the quota can be read from the pw_shell field of the vqpasswd struct) Onno

2 3

[Dovecot] Date error bug
by Bgs 12 Jun '07

12 Jun '07

Hi all, I encountered a bug, that prevents me from moving mail and as a side effect it messes up all thunderbird/mozilla mail clients (they won't do any message copy/move until I restart them). Here is the info and the header of the mail that produces the error (a spam mail): Dovecot version: 1.0.0 Mail header: Return-Path: <xxdwwu(a)boboakes.com> Delivered-To: bgs-hu-bgs(a)bgs.hu Received: (qmail 10895 invoked from network); 7 Jun 2007 16:51:21 -0000 Received: from unknown (HELO 86.109.208.58.broad.sz.js.dynamic.163data.com.cn) (58.208.109.86) by 0 with SMTP; 7 Jun 2007 16:51:21 -0000 Received: from [58.208.109.86] by INBOUND.BOBOAKES.COM.NETSOLMAIL.NET; Tue, 15 May 2085 16:51:38 -0800 From: Nigel <xxdwwu(a)boboakes.com> To: <bgs(a)bgs.hu> Subject: explore this offer Date: Tue, 15 May 2085 16:51:38 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_021F0ADE.78E00150" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Aca6Q09K1THIO7J1RUMI4LVVDU6VQF== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 . Message-ID: <021f0a9b$6abcc150$566dd03a@xxdwwu> Attached is the error window with the actual error message. It seems that the year 2085 date is not handled but dovecot. Regards Bgs PS: Probably unrelated but here are the other infos: Linux, local XFS, AMD Athlon XP, clients Seamonket 1.1.1 and Thunderbird 2.0.0.0

2 2

[Dovecot] SEGV when user over filesystem quota and "Move to Trash"
by Steffen Kaiser 12 Jun '07

12 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've configured Dovecot v1.0.0 with filesystem quota and to use hardlinks. Latter I use intentionally to save disk space and to achieve that an user can delete mails even if over quota and using the "Delete to Trash" feature. The following happens, when the directory file of .Trash/* fills up and would need to be expanded, but fails because of an over-quota condition. The crash is not so problematic, because you can wait some time (I guess until the lock of .Trash/dovecot-uidlist.lock expires) and you can delete mails from Trash to make room. However, there are leftover files in .Trash/tmp, what may make problems. First you get a "Out of quota" error in the MUA, maybe a second or a third time, too. Then: dovecot: Jun 12 09:10:38 Info: IMAP(dvtest) [3492]: copy -> Trash: uid=500, msgid=<cs-HoeqDW06gzBNu-9HdUBR4A@> dovecot: Jun 12 09:10:38 Error: child 3492 (imap) killed with signal 11 When you try to delete another mail: process #1: nanosleep({0, 158957000}, NULL) = 0 lstat64("/var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 time(NULL) = 1181630732 nanosleep({0, 170189000}, NULL) = 0 lstat64("/var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 time(NULL) = 1181630732 process #2: gettimeofday({1181630713, 945424}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 9335) = 0 gettimeofday({1181630723, 281935}, {4294967176, 0}) = 0 gettimeofday({1181630723, 282014}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 9999) = 0 gettimeofday({1181630733, 281949}, {4294967176, 0}) = 0 gettimeofday({1181630733, 282149}, NULL) = 0 .Trash/tmp contains 28 items (growing) After the "Connection timeout" error in the client process #1 still loops repeatedly. Eventually the processes stops. Maybe it is waiting for the release of the lock by the process killed by segv? Finally it dumps core, too. dovecot: Jun 12 09:10:38 Info: IMAP(dvtest) [3821]: copy -> Trash: uid=500, msgid=<cs-HoeqDW06gzBNu-9HdUBR4A@> dovecot: Jun 12 09:12:39 Error: child 3821 (imap) killed with signal 11 Core was generated by `imap [dvtest 10.20.10.63]'. Program terminated with signal 11, Segmentation fault. #0 maildir_sync_get_keywords_sync_ctx (ctx=0xffffffff) at maildir-sync.c:242 242 { (gdb) bt #0 maildir_sync_get_keywords_sync_ctx (ctx=0xffffffff) at maildir-sync.c:242 #1 0x0806ddd4 in maildir_mf_get_path (ctx=0x0, mf=0x20) at maildir-save.c:263 #2 0x0806de80 in maildir_transaction_unlink_copied_files (ctx=0x80fcbb0, pos=0x0) at maildir-save.c:477 #3 0x0806e5cb in maildir_transaction_save_commit_pre (ctx=0x80fcab0) at maildir-save.c:561 #4 0x080693c4 in maildir_transaction_commit (_t=0x8101eb8, flags=0) at maildir-transaction.c:28 #5 0xb7ddbbd0 in quota_mailbox_transaction_commit (ctx=0x8101eb8, flags=0) at quota-storage.c:74 #6 0x08057965 in cmd_copy (cmd=0x80df0f0) at cmd-copy.c:124 #7 0x0805b1be in cmd_uid (cmd=0x80df0f0) at cmd-uid.c:19 #8 0x0805b728 in client_handle_input (cmd=0x80df0f0) at client.c:335 #9 0x0805b7b7 in client_handle_input (cmd=0x80df0f0) at client.c:389 #10 0x0805be3c in _client_input (context=0x80df0a8) at client.c:432 #11 0x080bc902 in io_loop_handler_run (ioloop=0x80dc9b0) at ioloop-poll.c:199 #12 0x080bbb58 in io_loop_run (ioloop=0x80dc9b0) at ioloop.c:326 #13 0x08063e80 in main (argc=Cannot access memory at address 0x0 ) at main.c:290 I also managed it to have to two processes waiting for /var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock. dovecot -n: # /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/ca.crt ssl_cert_file(default): /etc/ssl/certs/imap.pem ssl_cert_file(imap): /etc/ssl/certs/imap.pem ssl_cert_file(pop3): /etc/ssl/certs/pop3.pem ssl_key_file(default): /etc/ssl/private/imap.key ssl_key_file(imap): /etc/ssl/private/imap.key ssl_key_file(pop3): /etc/ssl/private/pop3.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_log_format_elements: %p: user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle: yes first_valid_uid: 1000 mail_location: maildir:%h/MailDir:CONTROL=/var/cache/dovecot/%i/control:INDEX=/var/cache/dovecot/%i/index mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib mail_plugins(imap): quota imap_quota mail_log zlib mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 0 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: . inbox: yes hidden: yes auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /etc/passwd socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 432 group: mail plugin: quota: fs Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRm5VCi9SORjhbDpvAQLDQwgAp0Zcg4SbTXXyFTUFVsxRHjhRr1V2ZuoE Ajpar7u5hoG8IfJ8u6noxk2XvNlD0rL0g/oXHJDeRTuZs6PVwcQpSEyQ0DNUx8BY bUyX5i3sR02MOrwbKvlq6ynvV3VE5PY4fpgCfqUv7ZE4W72u577IQ4l/C3+hgC+Y qzKw2URlVzoJj6apyXEIZcv4gvxkxl4mMtOmoXrTj5nMfz7EFbbuXuK9aYfFhLFp YB/Q0FxsU3YylpYYbFGronbmrAUGb2TCJckRAwDdTzT1s++6uvbJt5BLRnwiOK6H UAEuJJllwoDcwx0WIwMzf3SXP52OSqHdEVBuJprxpHrTI7Fe2fm5FA== =WkkL -----END PGP SIGNATURE-----

2 2

[Dovecot] Cannot get cmusieve to work
by Dani 12 Jun '07

12 Jun '07

Hi, # I messed with the identities in my MUA and sent the email with a non registered address, sorry for the incinvenience ## I'm not able to make cmusieve to work to filter emails. Below is my configuration. I'm using a .dovecot-sieve example from the wiki: require "fileinto"; if exists "X-Spam-Flag" { fileinto ".Junk/"; } I've been following (as acurately as I could) the documentation, tuts and examples. I found this in the dovecot list: http://www.dovecot.org/list/dovecot/2007-March/020674.html and I used the CONCAT method but anyway mails don't filter because of two "//". *********LOGS******** Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): Loading modules from directory: /usr/lib/dovecot/modules/lda Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: dani(a)exampledomain.org Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: maildir=dani(a)exampledomain.org/ Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: uid=110 Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: gid=8 Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: home=/home/vmail/exampledomain.org/dani@exampledomain.org/ Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): maildir: data=/home/vmail/exampledomain.org/dani@exampledomain.org Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): maildir: root=/home/vmail/exampledomain.org/dani@exampledomain.org, index=/home/vmail/exampledomain.org/dani@exampledomain.org, control=, inbox= Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): cmusieve: Using sieve ****path: /home/vmail/exampledomain.org/dani(a)exampledomain.org//.dovecot.sieve*** Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): msgid=<20070612110825.F38F61054E8(a)sc8-sf-spam1.sourceforge.net>: saved mail to INBOX I've been looking into the problem and I must have forget something obvious, but I cannot make it work. does anyone can point me to the problem? thanks in advance. Dani CONFIGS ************** dovecot --version 1.0.0 (debian) ************** ******************** # /etc/dovecot/dovecot.conf protocol lda { postmaster_address = postmaster(a)exampledomain.org mail_plugin_dir = /usr/lib/dovecot/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve } *************** dovecot-sql.conf *************driver = mysql connect = dbname=postfix user=postfix password=qwe123dsazxc port=3306 host=localhost default_pass_scheme = CRYPT password_query = SELECT password FROM mailbox WHERE username ='%u' user_query = SELECT maildir, 110 AS uid, 8 AS gid, CONCAT('/home/vmail/%d/', @home := maildir) AS home FROM mailbox WHERE username = '%u

2 2

[Dovecot] per mailbox maildir format
by Bgs 12 Jun '07

12 Jun '07

Hi all, Is it possible to set the maildir format at mailbox level? I'd like to us Maildir++ for most of my clients, but want to emulate the other one for one of my users. Can this be done with dovecot? Thanks Bgs

2 2

[Dovecot] how to create new user account
by santhosh 12 Jun '07

12 Jun '07

Hi, I am using dovecot1.0.0. How to create new user in dovecot ? Thanks in advance Regards, Santhosh

3 2