- dovecot - dovecot.org

[Dovecot] FC4 and Dovecot 1.0 not displaying all migrated mailboxes
by Lovell Mcilwain 02 Nov '06

02 Nov '06

Hello all, I recently switched to dovecot on my FC4 server from UW-IMAP on my Mac OS X 10.3 machine and I was able to get my inbox and my trash box to be seen without any issues but all of my other mailboxes don't seem to show up. My mail directory is ~/mail and that is where I placed all of my mailboxes that I moved from my mac, but when I log into my new server using SSL/IMAP, only my trash and my inbox show up. My other mailboxes don't show up at all. Can anyone tell me how I can get my other mailboxes to show? As far as I know these mailboxes are standard unix mailbox files. Thanks

2 1

[Dovecot] another suggestion
by Hans Morten Kind 02 Nov '06

02 Nov '06

On our solaris systems we quite often sees dovecot coredump on exit when trying to free a null buffer. After including if (array->buffer == NULL) return; in array_free() in array.h these coredums have been avoided. hmk

2 1

[Dovecot] BUG in RC10 deliver using mbox format
by Steven F Siirila 02 Nov '06

02 Nov '06

After recently adding the -f parameter to the call to the deliver command which is called by Postfix, I found that e-mail with a null return path (MAIL FROM:<>) was causing Dovecot deliver to SEGFAULT. I verified this by making this patch to deliver.c (notice I fixed a typo here, too): *** deliver.c.orig Fri Oct 13 07:32:28 2006 --- deliver.c Fri Oct 27 21:26:08 2006 *************** *** 446,454 **** i++; if (i == argc) { i_fatal_status(EX_USAGE, ! "Missing envleope argument"); } ! envelope_sender = argv[i]; } else { print_help(); i_fatal_status(EX_USAGE, --- 446,455 ---- i++; if (i == argc) { i_fatal_status(EX_USAGE, ! "Missing envelope argument"); } ! if (*argv[i]) ! envelope_sender = argv[i]; } else { print_help(); i_fatal_status(EX_USAGE, While this fixed my SEGFAULT, it still leaves the "From_" line with the default "dovecot.deliver" as the return path, something I don't want. It should be "MAILER-DAEMON" or some-such just like all the other LDAs in the case of a NULL return path. Perhaps there needs to be a new parameter so one can specify what a NULL return path should be converted to when it is encountered... Also, note that the "Usage" message in deliver.c does not include the relatively new -f option either, so that should have been part of my above patch as well. -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

3 2

[Dovecot] quota with sendmail and dovecot
by Antonio Casado Rodríguez 02 Nov '06

02 Nov '06

I have a problem with dovecot and quotas I don't want quota in INBOX with sendmail (mbox), it's work ok. Sendmail can put the new messages in INBOX although exceed the quota limit. I have two namespace in dovecot: namespace private { separator = / inbox = yes prefix = "#mbox/" location = mbox:/Public/Maildir/%n_mbox_indexes:INBOX=/var/mail/%n } namespace private { separator = / prefix = "" location = maildir:/Public/Maildir/%n } I have this quota: plugin { quota = maildir:storage=10240 } It's work ok, i have 10 MB in INBOX and i have 10 MB in maildir. My clients are Mozilla Thunderbird My problem: when Sendmail put one new message in INBOX, Thunderbird see it, but the quota don't change. I think that when dovecot do a full sync it must update the quota.

2 1

[Dovecot] mbox_sync_read_and_move failure
by Timothy Daly 02 Nov '06

02 Nov '06

Hi, I recently switched to using dovecot for my IMAP server. I'm running dovecot 1.0rc10 on redhat linux 7.3. The filesystem is ext2, not NFS. I'm using mbox for mail storage. It worked okay for a day or two, but now when I try to check my mail I get an error from evolution, my imap client, saying that the server unexpectedly disconnected. In the server logs I see: Nov 2 13:10:49 tenkan dovecot: imap-login: Login: user=<tim>, method=PLAIN, rip=192.132.92.15, lip=216.114.78.229, TLS Nov 2 13:10:58 tenkan dovecot: IMAP(tim): file mbox-sync-rewrite.c: line 405 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Nov 2 13:10:58 tenkan dovecot: child 30315 (imap) killed with signal 6 I see that this came up on this list a little while ago, but it doesn't sound like it got resolved. For the moment, I'm unable to read my mail via IMAP. :/ Any ideas? Cheers, Tim ____________________________________________________________________________________ Access over 1 million songs - Yahoo! Music Unlimited (http://music.yahoo.com/unlimited)

1 1

[Dovecot] Dovecot-auth stand alone
by Jorgen Lundman 02 Nov '06

02 Nov '06

Since you have to have a SASL implementation with Postfix, either Cyrus or Dovecot, would it be feasable to have autoconf options to build only those parts required? Currently I attempt to disable most things, except for LDAP which we want to use: ./configure --with-ldap --without-pop3d --without-passwd --without-passwd-file --without-shadow --without-pam --without-checkpassword --without-bsdauth --without-vpopmail --without-ssl --without-deliver --without-sql-drivers --with-storages= That still compiles, and installs, imap. No way to stop that. However, master process "dovecot" does not want to start with "protocols=" set to empty. This is somewhat understandable, but I really do not want any listening ports, just the Unix auth socket and dovecot-auth process. Bind localhost for now? I take it I should run dovecot-auth as stand-alone, setting the AUTH_1 environment variable as well as a few others. Lund -- Jorgen Lundman | <lundman(a)lundman.net> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home)

3 5

[Dovecot] 1.0.rc10 status report
by David Lee 02 Nov '06

02 Nov '06

(Background: Relatively new to dovecot; looking to do transparent replacement of long-established UW-IMAP on cluster of Linux boxes which NFS-mount a shared "/var/spool/mail".) With rc8, where I had already increased "login_max_processes_count" from default 128 to 1024, we had still hit the issue of too many logins crashing dovecot, so that trial had only lasted a couple of hours. With rc10, I doubled this to try to avoid the problem (I didn't want to risk testing the new code that addressed the problem... sorry!). We ran for almost a full working day. Good! Because of a few issues (below) I then backed off. 1. "User unknown": We use NIS for our passwd information. On the earlier rc8 test we had had several occurences of "User unknown" (from "deliver") giving "dsn=5..." for perfectly valid users. So for this rc10 test I applied a local patch so these were reduced to "EX_TEMPFAIL" (dsn=4...). (This was triggered, as epected, a few times and subsequent delivery attemtps succeeded.) I strongly suspect that this is some sort of issue with FC5, probably "nscd" and nothing to do with dovecot. Hints would be nice, but from the dovecot perspective you may probably ignore this item. 2. For one particular user, the "deliver" consistently gave: Failed to create storage for '...' with mail 'mbox:/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB:INBOX=... I think this is ultimately due to something strange in the user ".forward" file. I'd be delighted to follow this up with anyone else who might have seen it. Although in one sense we may be drifting off-topic, in another sense I suspect that there is scope for adjusting "deliver" to handle this more gracefully. 3. There were several occurences of: IMAP(...): file ../../../../../src/lib-storage/index/mbox/mbox-sync-rewrite.c: line 405 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) child 30842 (imap) killed with signal 6 This looks particularly awkward. Any thoughts? 4. There were two occurences of: IMAP(...): file ../../../src/lib-index/mail-index.c: line 1801 (mail_index_move_to_memory): assertion failed: (index->fd == -1) child 20493 (imap) killed with signal 6 Again, this looks particularly awkward. Any thoughts? For these last two items, note that the indexes are currently NFS-shared alongside the INBOX area. I'm still not clear on how to regard the concept of indexes, as applied to a small cluster of machines, and handling simultaneous updates to INBOXes (analogous to the vital importance of INBOX locking for such updates). If one imagines the IMAP daemon (and pop and deliver) as file-clients of the (NFS-shared) INBOXes on a fileserver, do the indexes belong very close to the INBOXes (fileserver) or the dovecot software (file client)? So should I have the indexes on the fileserver (one instance), or should they be on each cluster machine's private storage (possibly several instances; one per cluster machine)? I've got them on the server; would they be better on the cluster clients? (Might that be the cause and fix of these two problems?) -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

3 2

[Dovecot] deliver + quota failure
by Mark Ruijs 02 Nov '06

02 Nov '06

I use Dovecot's deliver as the LDA for Postfix in a virtual user setting. My maillog reads: Oct 22 00:17:51 mail dovecot: auth(default): master in: USER 1 mark.ruys(a)in2sports.net service=deliver Oct 22 00:17:51 mail dovecot: auth-worker(default): sql(mark.ruys(a)in2sports.net): SELECT maildir AS home, 5000 AS uid, 5000 AS gid, CONCAT('dirsize:storage=', round(quota/1000)) AS quota FROM mailbox WHERE username = 'mark.ruys(a)in2sports.net' AND active = 1 Oct 22 00:17:51 mail dovecot: auth(default): master out: USER 1 mark.ruys(a)in2sports.net home=in2sports.net/mark.ruys/ uid=5000 gid=5000 quota=dirsize:storage=10240 Oct 22 00:17:51 mail deliver(mark.ruys(a)in2sports.net): msgid=<00c801c6f55e$af416fb0$8801a8c0@Moskou>: save failed to INBOX Oct 22 00:17:51 mail deliver(mark.ruys(a)in2sports.net): open(in2sports.net/mark.ruys//.temp.mail.in2sports.net.12777.5c70c02bb158bd1 a) failed: No such file or directory The reason is, I'm out of quota. I expected some kind of bounce, but the message is killed by Amavis because of a bad header: Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Quota exceeded --12684/mail.in2sports.net Content-Type: message/disposition-notification Reporting-UA: mail.in2sports.net; Dovecot Mail Delivery Agent Final-Recipient: rfc822; mark.ruys(a)in2sports.net The problem is, there is no recipient (header is missing). Anyone a clue how to fix it? Thanks for some directions. Mark Ruys Config: - Dovecot rc 10 - postfix-2.3.3-2.mysql.sasl2.vda.fc4 dovecot.conf: protocol imap { mail_plugins = quota imap_quota } protocol lda { postmaster_address = postmaster(a)in2sports.net mail_plugins = quota auth_socket_path = /var/run/dovecot/auth-master } postfix/main.cf: dovecot_destination_recipient_limit = 1 virtual_transport = dovecot virtual_create_maildirsize = yes virtual_mailbox_limit_maps = mysql:/etc/postfix/mysql/limits.cfg virtual_mailbox_limit_override = yes virtual_overquota_bounce = yes

2 1

[Dovecot] valid_chroot_dirs question
by Luca Corti 02 Nov '06

02 Nov '06

Hello, I've got a dovecot setup using PAM and real system users. In this setup I also use pure-ftpd to give local users ftp access to their $HOMEs. To have pure-ftpd chroot into the user home i replaced /home/user with /home/user/./ in /etc/passwd. Unfortunately this breaks Dovecot this way: Oct 23 18:18:20 localhost dovecot: Invalid chroot directory '/home/foo' (user foo) (see valid_chroot_dirs in config file) and dovecot.conf says # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = Now if I set valid_chroot_dirs = /home everything works, but the WARNING pretty much scares me since user foo HAS shell access. Is this safe? Is there a way to avoid this? Why I can't chroot to /home/foo/./ if I can to /home/foo ? I'm on 1.0rc10 thanks

2 1

[Dovecot] Dovecot imap bug
by Lauri Jesmin 02 Nov '06

02 Nov '06

Hello, i got such error from dovecot RC10, Oct 24 10:38:58 raud dovecot: [ID 107833 mail.info] imap-login: Login: user=<eleppik>, method=PLAIN, rip=xxx, lip=yyy Oct 24 10:39:03 raud dovecot: [ID 107833 mail.error] IMAP(eleppik): file mbox-sync-rewrite.c: line 405 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) This is Solaris on x86, 32 bit executable, compiled with gcc, and there is enough room for index creation. -- Lauri Jesmin <lauri.jesmin(a)ut.ee> Tartu Ülikool

2 1