Re: [Dovecot] Password Problems
On Thu, 2007-05-03 at 10:15 -0700, Don O'Neil wrote:
I have a user that has a password that has {} in it (left and right curly
brackets). Under earlier versions of dovecot (less than v1) there weren't
any problems with it. Now that we've upgraded to v1, his password no longer
work. The short term solution is for him to change his password, which he
has. Has anyone else seen this same problem? It seems to pop up more when
using webmail apps such as Squirrelmail or Uebiumaiu.
If password begins with '{' then Dovecot treats it as
{scheme}password. Otherwise { and } inside the password shouldn't
matter. It's possible to have '{' as the first character in password if
you make your passdb return the {scheme} prefix always. I guess you're
storing passwords as plaintext, because otherwise this shouldn't be a
problem at all. So make sure all passwords have a {plain} prefix.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] INBOX inaccessible
On Thu, 2007-05-03 at 11:27 +0200, Sophie Nicoud wrote: One of my users can't read message of his Inbox, he can view subject of message with Thunderbird or Squirrelmail and IMAP but when he click on a message in order to read it he has thess messages with Thunderbird : The current command did not succeed. Invalidmessageset: 1181461470:-1181461446. I just wrote this wiki page: http://wiki.dovecot.org/Clients/NegativeUIDs Upgrading Dovecot or deleting index files won't fix it, although upgrading is a good idea anyway. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] input / output error in dovecot.log
On Thu, 2007-05-03 at 14:15 +0800, Joe Wong wrote: From time to time, I saw input / output error on rename() or pwrite_full(), for example: dovecot: May 02 05:46:18 Error: IMAP(joe): rename(/fs/joe/Maildir/.Sent Items/tmp/1178084777.P21895Q0M200058.tkodog.no-ip.com.com, /fs/joe/Maildir/.Sent Items/cur/1178084777.P21895Q0M200058.tkodog.no-ip.com:2,S) failed: Input/output error .. What could be the cause of this problem and the consequences? Your hard disk is dying (or the network with NFS)? Syscalls should never return I/O error unless something's really wrong. dmesg most likely gives additional information. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Strange Mail Problem
On Wed, 2007-05-02 at 09:13 -0400, Jason Baker wrote: I submitted this question to the Postfix maillist and they suggested that I post to this one. Here's my issue: I have a Postifx email system running on a CentOS 4 box, with Dovecot pop3 and imap. Last week, one of my users reported to me that about a dozen emails suddenly showed up in his in box (as unread messages), but none of them were addressed to him. Under further investigation, they turned out to be from another user's inbox. The messages were all over a month old. How could mail simply show up in one inbox from another user's? We're using Mozilla Thunderbird 1.5. Anyone else run into issues like this? nss_ldap? http://wiki.dovecot.org/AuthDatabase/Passwd signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Switching from mailbox to maildir.. duplicates!
On Wed, 2007-05-02 at 11:32 +0200, Lars Johansen wrote: I have done some testing transfering the mail with the mb2md script, the conversion works correctly, but users gets duplicates since they selected keep mail on server I have googled for the problem, and set pop3_reuse_xuidl=yes and pop3_uidl_format = %08Xu%08Xv is the same on both servers.. but no luck. My first tought was to script in an X-UIDL header for each mail that was converted.. but that wont work since the mail already downloaded by the client didnt contain that header.. It doesn't matter if the client hasn't seen the X-UIDL header, because it's Dovecot that uses it. The problem is anyway that your mbox - maildir conversion didn't preserve the UIDVALIDITY and UIDs. I'm not aware of any existing conversion script that can preserve them. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] PATCH: Deliver looses mail and DSN if Return-Path is missing
On Wed, 2007-05-09 at 10:05 +0200, Steffen Kaiser wrote: - --- src/deliver/mail-send.c (revision 47) +++ src/deliver/mail-send.c (working copy) @@ -42,7 +42,7 @@ i_info(msgid=%s: Return-Path missing, rejection reason: %s, orig_msgid == NULL ? : str_sanitize(orig_msgid, 80), str_sanitize(reason, 512)); - - return 0; + return EX_TEMPFAIL; } I actually did the exact opposite change a few months ago :) 2007-03-26 00:24 Timo Sirainen [EMAIL PROTECTED] * src/deliver/mail-send.c: If we couldn't send a bounce because of a missing Return-Path header, just return success instead of failing with EX_TEMPFAIL. I'm not sure why I changed that. I think this is a problem only if the SMTP server is misconfigured not to add the Return-Path header? In that case I'll change the above i_info() to i_error() also.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] PATCH: Deliver looses mail and DSN if Return-Path is missing
On Wed, 2007-05-09 at 11:40 +0300, Timo Sirainen wrote: On Wed, 2007-05-09 at 10:05 +0200, Steffen Kaiser wrote: - --- src/deliver/mail-send.c (revision 47) +++ src/deliver/mail-send.c (working copy) @@ -42,7 +42,7 @@ i_info(msgid=%s: Return-Path missing, rejection reason: %s, orig_msgid == NULL ? : str_sanitize(orig_msgid, 80), str_sanitize(reason, 512)); - - return 0; + return EX_TEMPFAIL; } I actually did the exact opposite change a few months ago :) 2007-03-26 00:24 Timo Sirainen [EMAIL PROTECTED] * src/deliver/mail-send.c: If we couldn't send a bounce because of a missing Return-Path header, just return success instead of failing with EX_TEMPFAIL. I'm not sure why I changed that. I think this is a problem only if the SMTP server is misconfigured not to add the Return-Path header? In that case I'll change the above i_info() to i_error() also.. Oh, right, return_address = NULL also if the address isn't valid. In those cases I think it should return 0, because there just isn't anything to be done. So EX_TEMPFAIL should only be returned if the whole Return-Path: is missing I think. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] .imap files
On Tue, 2007-05-08 at 08:17 -0400, L. Scott Loftin wrote: I have recently upgraded from Fedora Core 4 to Fedora Core 6 (the FC6 was a clean install, not an upgrade). Prior to the upgrade, I used Dovecot to handle IMAP email that talked to Outlook clients. After the FC6 install and copying the .imap* files to the newly recreated user accounts, Outlook is not seeing the old email. Dovecot is creating new dovecot.* files to hold new email, not looking in the existing .imap.* files. There are various reasons why mailboxes aren't showing. http://wiki.dovecot.org/MissingMailboxes lists some of them. Is there a way to either convert the .imap* files into the new dovecot.* files or any way to recover the email that anyone knows about? .imap* files however have nothing to do with mail not showing up. There's no need to convert or do anything to them. If anything you can just delete them. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] ldap and digest-md5 problem
On Sat, 2007-05-05 at 16:13 +0200, Łukasz Mierzwa wrote: May 5 16:03:32 srv dovecot: auth(default): digest-md5 ([EMAIL PROTECTED],127.0.0.1): password mismatch .. It seems that client and dovecot hashes calculated for DIGEST-MD5 are different, I tested squirrelmail 1.4.9a, kmail 3.5.6 both can't login using digest-md5 so maybe dovecot does not working correctly? Passwords where created using phpldapadmin and clear password type, cram-md5 logins are ok. I can't find any info on ldap and digest-md5 incompatibility in dovecot wiki, can anyone give my a hint? I'm guessing they're using a different username in the hash calculation. DIGEST-MD5 hashes are a bit special because they contain the username also in them. auth_default_realm = pcserwis.net auth_username_format = %Lu If you're not logging in as lowercased [EMAIL PROTECTED] that's the problem. Or any other mismatch in the username as well. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Tru64 patch for mountpoint.c
On Sat, 2007-05-05 at 10:19 +1000, Simon L Jackson wrote: I believe that there is one more patch required for a successful build on Tru64: Thanks, applied the patch. And sorry, forgot to mention your name in the commit message.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] [courier-dovecot-migrate.pl] - No such file or directory at courier-dovecot-migrate.pl line 230
On Tue, 2007-05-01 at 02:54 +0200, Luca Corti wrote: On Mon, 2007-04-23 at 12:07 -0700, Troy Engel wrote: Try running the script under strace (i.e. 'strace -e trace=file perl /script.pl') or truss to watch the perl script and see what file or directory it's trying to open. That should provide a quick clue. I was just testing the migration script, encountered the same issue and just added a print before the open || die at line 230. It tries to open the file Maildir/courierimapkeywords/:list which seems to be missing and probably not mandatory. I'm on Courier-IMAP 4.1.1. The patch below solves this. Is this a bug in the script? I solved it a bit differently, uploaded v1.0.1 to http://dovecot.org/tools/ signature.asc Description: This is a digitally signed message part
Re: [Dovecot] lda reports a lot of errors
On Sun, 2007-04-22 at 23:53 +0200, Thomas Balsfulland wrote: hello, i am using dovecot 1.0.rc15-1~bpo1 (from backports.org) on an debian sarge machine as lda imapd and pop3d with postfix 2.1.5-9. sometimes docvecot lda cannot write an mail to an existing mbox-file and the logfiles fills up with: deliver([EMAIL PROTECTED]): 2007-04-22 23:17:32 Error: Cached message offset 6937844 is invalid for mbox file /home/vmail/domain.tld/user1 You seem to be using maildir++ quota with mboxes. Does that actually work? I never intended it to work at least. :) Anyway there have been a lot of mbox fixes since rc15. Also there has been one mbox+quota fix after v1.0: http://dovecot.org/list/dovecot-cvs/2007-April/008722.html With v1.0 + the above patch this invalid mbox offset error should never happen anymore. 40 lines from this per second and will never stop! I'm not sure why it would do infinite looping though, although I do remember fixing one such problem with mboxes at some point. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] IMAP freezing on OSX
On Sun, 2007-05-06 at 13:49 +0100, Ben Carter wrote: The problem /seems/ to often start as a result of trying to move messages between folders. I'm not certain if that's a root cause, though, or simply a consequence of opening an affected folder to perform the move. I have a spam folder with a large number (1) of messages in it, and trying to file stuff in there is a relatively surefire way to generate the problem. Try if dotlock_use_excl=yes helps. That setting was made to fix hard linking problems with HFS. Otherwise http://wiki.dovecot.org/Debugging/ProcessTracing might show up something useful when looking at what imap process is doing at the time it seems to be hanging. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] PATCH: Deliver looses mail and DSN if Return-Path is missing
Steffen Kaiser schrieb: BTW: Would it be possible to return the errno of the failed system call to the MTA via the main() return value? I believe that any MTA will act upon these codes and the postmaster can setup the preferred way handling bounces. No, the any MTA - excluding qmail and other incompatible stuff(*) - will act upon sysexits.h values, not errno values (which are often outside the range for exit codes anyway). (*) at least it treats EX_TEMPFAIL (75) as temporary failure.
Re: [Dovecot] PATCH: Deliver looses mail and DSN if Return-Path is missing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 9 May 2007, Matthias Andree wrote: No, the any MTA - excluding qmail and other incompatible stuff(*) - will act upon sysexits.h values, not errno values (which are often OK, no objection - sysexit.h. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkG2tC9SORjhbDpvAQK1JggAnwcpu2s59Tda2Rn9wC/WxijERCofrxQ7 nIJi8jQ0Hoo8/lhJrEfMC6Ekgz7DVdgsvhujGKZ8GY5S5pxBrs2MHI9x5FegqhPq Rvb6K723kSMiuVf+Xn0NX7zoAbsEjgVy7ltd9G8M4qCAmSFKs7/ATKL5ith8vM01 Ifngi8xjZgdiuWfB5YpCCLVDus4J371cQjZeDOSwAG5ZPD2D6uib9JS4MdZQ/RAm 3C4j4igGYjGc1eRFyXjVe+5ZOrsOycHqA/l+FqJQ9SZA3oIZFlDrqjSA/xpCEmA3 F+lW0+i7sgCooe+T5BNiV3s7XawZeNe3HL1WsfGUiOW0AQlNsM9/9g== =wiif -END PGP SIGNATURE-
Re: [Dovecot] IMAP freezing on OSX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 9, 2007, at 2:35 AM, Timo Sirainen wrote: * PGP Signed by an unknown key On Sun, 2007-05-06 at 13:49 +0100, Ben Carter wrote: The problem /seems/ to often start as a result of trying to move messages between folders. I'm not certain if that's a root cause, though, or simply a consequence of opening an affected folder to perform the move. I have a spam folder with a large number (1) of messages in it, and trying to file stuff in there is a relatively surefire way to generate the problem. Try if dotlock_use_excl=yes helps. That setting was made to fix hard linking problems with HFS. Otherwise http://wiki.dovecot.org/Debugging/ProcessTracing might show up something useful when looking at what imap process is doing at the time it seems to be hanging. Is this a setting in dovecot.conf? I'm using all the defaults, there, myself. Jon -BEGIN PGP SIGNATURE- Version: PGP Universal 2.6.1 Charset: US-ASCII wj8DBQFGQbp6sTedWZOD3gYRAtP1AJ9ly++iRdNDFWs+dHm+zzkB8WRIswCgwZoI NrQmAuBDvMhF65FxLI2e6FY= =8qPy -END PGP SIGNATURE-
Re: [Dovecot] .imap files
L. Scott Loftin wrote: Thanks for the quick answers. My problem isn't about new email now showing up after the FC4--FC6 upgrade. It's about trying to get to old email (that existing under FC4 (Dovecot 0.99.14) not being accessible in any way under FC6 (Dovecot 1.0.0). If I delete the .imap.* files from 0.99.14, I lose all the old email in the folders. Email under 1.0.0 is working perfectly (new mail shows up and is perfectly readable by the client). I just need to find a way to get back to the old email from 0.99.14's .imap* files. You can't. That is not where the mail is stored. Dominic
Re: [Dovecot] sporadic slow/non response, problems copying to sent folder
On Fri, 2007-05-04 at 09:23 -0700, Danno Coppock wrote: May 3 21:32:08 tejas dovecot: IMAP(annie): Disconnected for inactivity I don't think these should happen. Do you have a stateful firewall killing the idling connections? The slowdowns would then be caused by the client waiting for a reply from the server which never comes because firewall is blocking the connection. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Hot to get rid of \DON\'T DELETE THIS MESSAGE\ messages?
On Thu, 2007-04-26 at 14:09 +0300, [EMAIL PROTECTED] wrote: I'm using Dovecot 1.0.0 (mbox) with Postfix 2.4 on my FreeBSD box, as a pop3-only server (imap is disabled). All account mailboxes are accessed using Outlook clients. I've noticed that, whenever I'm retrieving mail with pop3, a DON'T DELETE THIS MESSAGE is created in mbox. Although these messages are never sent to client MUAs, I found them very annoying. BTW I don't use (or used before) UW or Pine or any other c-client, therefore I assume it's a Dovecot issue. Previously I was using Cyrus and never had such a problem. Any idea how this can be fixed? It's a feature. You can't get rid of them. They're especially important with IMAP to avoid untrusted messages from messing Dovecot's UIDs. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Inconsistent Mailbox with Eudora as POP3 client
On Fri, 2007-04-27 at 11:28 +0200, Amon Ott wrote: The mail syslog shows e.g.: Apr 27 08:50:26 gateway dovecot: POP3(mk): Disconnected: Mailbox is in inconsistent state. top=0/0, retr=0/0, del=0/715, size=20210522 Anything else? This inconsistent state error just means that an error occurred earlier. It doesn't tell anything about the actual problem. And note that the above message was written to info log, which might be different from error log. See http://wiki.dovecot.org/Logging signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Trying to modify the source - fopen problems
On Fri, 2007-04-27 at 08:58 -0500, Phillip T. George wrote: Anyways, I'm trying to modify the dovecot source a bit, but the problem I'm having is that whenever I use fopen, it always returns NULL. I've tried a variety of things, even fopen(/dev/null, w) -- because that should almost always work. I'm trying to get it to work in src/pop3-login/client-authenticate.c pop3-login is chrooted, so there's no /dev. You could of course set login_chroot=no Any idea why this might be happening? Any suggestions as to where to put the code instead? (I'm trying to check the username against some information in a file OR pass the username to a process and have it do the work) dovecot-auth would be the correct place to do the authentication. Maybe you want to use a checkpassword script (http://wiki.dovecot.org/PasswordDatabase/CheckPassword). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] assertion failed
On Wed, 2007-05-02 at 14:10 +0200, Jan-Frode Myklebust wrote: On 2007-04-26, Adrian Stoica [EMAIL PROTECTED] wrote: What is this ? We just saw the same fault today when we switched from courier to dovecot on a large system today. The ~username/dovecot-uidlist contained: 1 -1 0 and deleting this file plus it's lockfile seems to have fixed the problem for the two users this happened for. Fixed it to log an error instead in such situations: http://dovecot.org/list/dovecot-cvs/2007-May/008728.html signature.asc Description: This is a digitally signed message part
[Dovecot] Conflict - Dovecot + Maildrop (maildirsize)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having some problems with quota from sql (maildir++) and dovecot + maildrop. I'm using maildrop for MDA and dovecot as IMAP server. When an e-mail arrives, maildrop calculates the quota and updates the 'maildirsize' file. When i use dovecot (webmail, thunderbird) it updates the 'maildirsize' too, overwriting it, but in a different way. Both programas don't use the same pattern for 'maildirsize'. Let me show: 'maildirsize' with maildrop: 1073741824S 117395679 1760 36751 36751 16101 16121 32222 96411 96411 53011 64151 117162 154191 154191 'maildirsize' with dovecot: 1099511627776S 585847701 102542 5504023 959 In both examples the quota is 1GB (1073741824S). And now ? Does anybody known how to fix that ? thanks - -- - Roberto Gonzalez Azevedo Rio de Janeiro, Brazil -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGQcttF+EMwkXLsEwRAoUOAKC0VXeC4USHyxOhsE5TQixk77hpmwCgxk5P ABOk8XHurCx/gEnd5StCkB8= =B+0f -END PGP SIGNATURE-
Re: [Dovecot] read only bug?
Hello, off The boss is back: 10 replies in an hour :-))) /off Thanks for your reply. I split my mailboxes with mb2md which was a very bad decision: not every mailbox started with the INTERNAL FOLDER DATA email and it lost them. It seems to have mixed up the filesnames too, because ls 1154939281.5.pc1\,* | wc -l says 10 and they are different emails! Is there any way to make dovecot to not correct these? Or it is a very important that maildir files should have different basenames? Best wishes, A. Timo Sirainen On Fri, 2007-05-04 at 21:38 0200, Nagyon Almos wrote: rename(/home/store/oldmails/.personal/cur/1154939281.5.pc1.S=1879:2,S, /home/store/oldmails/.personal/new/1178307014.P8610Q0M347618.pc1) failed: Permission denied This doesn't happen normally. I think you have duplicates (same maildir basename) in the maildir and Dovecot is trying to fix it by renameing one of the files to a new base filename. I guess the error message should be updated to contain Couldn't fix a duplicate maildir filename. ___ Diszlexiás a gyermekem? - 25 kérdéses gyorsteszt (Hálás lesz utána, bármi is az eredmény!) http://www.varazsbetu.hu/diszlexiateszt/
Re: [Dovecot] PATCH: sendmail-like DSNs in Dovecot deliver (EX_TEMPFAIL always)
Steffen Kaiser schrieb: Hello, I've put together an always tempfail sendmail-like DSN report back patch. Because I don't know how to transform the rejection reason into sysexit.h codes, it always tempfails. Just read /usr/include/sysexits.h and pick the best fit, such as EX_NOPERM. 8-)
Re: [Dovecot] assertion failed
On 2007-05-09, Timo Sirainen [EMAIL PROTECTED] wrote: Fixed it to log an error instead in such situations: http://dovecot.org/list/dovecot-cvs/2007-May/008728.html Great, thanks! We just moved a large cluster (100k+ active accounts) from courier pop/imap to dovecot (v1.0.0), and used the courier-dovecot-migrate.pl to do the conversion of maildirs. A couple of other failures we've been hitting is: #1: deliver([EMAIL PROTECTED]): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view-hdr.messages_count == map-hdr.messages_count) deliver([EMAIL PROTECTED]): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_panic_handler+0x1c) [0x45d67c] - /usr/local/dovecot/libexec/dovecot/deliver [0x45d27c] - /usr/local/dovecot/libexec/dovecot/deliver(mail_index_sync_update_index+0x86f) [0x446abf] - /usr/local/dovecot/libexec/dovecot/deliver(mail_index_sync_begin+0x245) [0x444665] - /usr/local/dovecot/libexec/dovecot/deliver(maildir_sync_index_begin+0x45) [0x416885] - /usr/local/dovecot/libexec/dovecot/deliver(maildir_transaction_save_commit_pre+0x68) [0x41c778] - /usr/local/dovecot/libexec/dovecot/deliver(maildir_transaction_commit+0x70) [0x417730] - /usr/local/dovecot-1.0.0/lib/dovecot/lda/lib10_quota_plugin.so [0x2a9557c3a8] - /usr/local/dovecot/libexec/dovecot/deliver(deliver_save+0x100) [0x411360] - /usr/local/dovecot/libexec/dovecot/deliver(main+0xb62) [0x412132] - /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x307b11c3fb] - /usr/local/dovecot/libexec/dovecot/deliver [0x410b0a] #2: deliver([EMAIL PROTECTED]): file mail-index.c: line 983 (mail_index_sync_from_transactions): assertion failed: (hdr.messages_count == (*map)-hdr.messages_count) deliver([EMAIL PROTECTED]): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_panic_handler+0x1c) [0x45d67c] - /usr/local/dovecot/libexec/dovecot/deliver [0x45d27c] - /usr/local/dovecot/libexec/dovecot/deliver(mail_index_map+0x87) [0x43e5f7] - /usr/local/dovecot/libexec/dovecot/deliver(mail_index_sync_begin+0x9e) [0xbe] - /usr/local/dovecot/libexec/dovecot/deliver(maildir_sync_index_begin+0x45) [0x416885] - /usr/local/dovecot/libexec/dovecot/deliver [0x4173aa] - /usr/local/dovecot/libexec/dovecot/deliver(maildir_sync_last_commit+0x47) [0x4174c7] - /usr/local/dovecot-1.0.0/lib/dovecot/lda/lib10_quota_plugin.so [0x2a9557c3a8] - /usr/local/dovecot/libexec/dovecot/deliver(deliver_save+0x100) [0x411360] - /usr/local/dovecot/libexec/dovecot/deliver(main+0xb62) [0x412132] - /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x307b11c3fb] - /usr/local/dovecot/libexec/dovecot/deliver [0x410b0a] #3: deliver([EMAIL PROTECTED]): file maildir-save.c: line 520 (maildir_transaction_save_commit_pre): assertion failed: (first_uid != 0) deliver([EMAIL PROTECTED]): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_panic_handler+0x1c) [0x45d67c] - /usr/local/dovecot/libexec/dovecot/deliver [0x45d27c] - /usr/local/dovecot/libexec/dovecot/deliver [0x41c9ed] - /usr/local/dovecot/libexec/dovecot/deliver(maildir_transaction_commit+0x70) [0x417730] - /usr/local/dovecot-1.0.0/lib/dovecot/lda/lib10_quota_plugin.so [0x2a9557c3a8] - /usr/local/dovecot/libexec/dovecot/deliver(deliver_save+0x100) [0x411360] - /usr/local/dovecot/libexec/dovecot/deliver(main+0xb62) [0x412132] - /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x307b11c3fb] - /usr/local/dovecot/libexec/dovecot/deliver [0x410b0a] #4: dovecot: POP3([EMAIL PROTECTED]): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid prev_uid) dovecot: POP3([EMAIL PROTECTED]): Raw backtrace: /usr/local/dovecot/libexec/dovecot/pop3 [0x45d73c] - /usr/local/dovecot/libexec/dovecot/pop3 [0x45d03c] - /usr/local/dovecot/libexec/dovecot/pop3(maildir_sync_index+0x769) [0x417029] - /usr/local/dovecot/libexec/dovecot/pop3 [0x417171] - /usr/local/dovecot/libexec/dovecot/pop3(maildir_storage_sync_init+0x65) [0x4173c5] - /usr/local/dovecot/libexec/dovecot/pop3(client_create+0x15d) [0x4111dd] - /usr/local/dovecot/libexec/dovecot/pop3(main+0x554) [0x412fd4] - /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x389e61c3fb] - /usr/local/dovecot/libexec/dovecot/pop3 [0x410a2a] The deliver bugs are quite bad, as they lead to incoming messages getting bounced.. -jf
Re: [Dovecot] dovecot-dspam-integration
On Tue, 2007-05-08 at 04:06 -0600, Trever L. Adams wrote: You mean dspam as --deamon? Yes, that was the recommendation in the documentation stating it was highly recommended not to do the other method. So, yes, my postfix file calls amavisd (for clamscan) which feeds it back into postfix which then calls dspam. I don't use --daemon right now, it was crashing too much and losing mail. YMMV. Hmm. How did that mail end up in SPAM when it doesn't have a signature? I only move mail into SPAM that was classified by dspam as SPAM so hence also has a signature. As I see it, dspam creates its .sig files. I do not believe these are kept around long term. Therefore, it is possible that the signature file disappears before one could move something out of SPAM (or into it, but I don't care about that). Am I misunderstanding something? Well, you control how long the .sig files are kept around. I keep them a week longer than my spam folder contents. johannes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Duplicate emails with several clients
Erick Perez wrote: Hi, I'm using Centos 4.4 (which is redhat linux but free) that comes with dovecot-0.99.11-4.EL4. Upgrade... Sorry, but 0.99.x is just too old, and unsupported... -- Best regards, Charles
Re: [Dovecot] some clarification re: ACL?
Perhaps adopting Courier-IMAP's ACL specification might make sense? Tab is the delimiter instead of space, so spaces are allowed in identifiers. Also, negative permissions are possible (i.e. +r to grant read access, -r to disable it). Also, I believe precedence is based on the order of the rules in the file, so you could have the group permissions override the user permissions by placing the group constraint further down. Anyway, there's also probably some benefit in using a common ACL format... interoperability is a good thing (unless you're Microsoft). Regarding the group permissions not working, am I to understand that as of now they are implemented but don't actually do anything? i.e. how can I make use of the group constraints? Timo Sirainen wrote: On Wed, 2007-05-02 at 12:40 -0400, Matt Zukowski wrote: The ACL documentation is at http://wiki.dovecot.org/ACL is a bit vague... I'd be happy to update it myself, but I need some clarification: For example, I have a dovecot-acl file with: group=portal_admin lrw anyone l The page also contains Groups aren't currently supported, but only because the groups can't be specified in userdb currently. Secondly, what is the group-override identifier supposed to do? Updated the page: Group-override identifier allows you to override users' ACLs. Probably the most useful reason to do this is to temporarily disable access for some users. For example: user=timo rw group-override=tempdisabled Now if timo is in tempdisabled group, he has no access to the mailbox. This wouldn't be possible with a normal group identifier, because the user=timo would override it. Thirdly, are spaces and other special characters allowed in the group/username identifiers? Spaces unfortunately aren't. I was thinking about this myself also a while ago. I'm not sure what would be the best way to change the current format to support spaces. Other characters are allowed. This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. Le contenu du pr'esent courriel est privil'egi'e, confidentiel et soumis `a des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation.
[Dovecot] Email client dowloads previously read messages as new during migration.
I am migrating from UW to dovecot and using mbox. I have been able to find mbox to maildir migration information and tools; however, I have had little luck finding any tool or information for performing such a migration where I wish to keep mbox. ( I know I should migrate to MailDir, but in the case I wish to take baby steps.) I have setup dovecot pop3 communication and I go to my email client and everything works fine with the exception that all mail I have previously read (when using UW as my POP server) is downloaded again as NEW. Is there a way to prevent this from happening without setting my client to delete mail from server? thank you!
Re: [Dovecot] Email client dowloads previously read messages as new during migration.
Eric and Barbara Sammons spake the following on 5/9/2007 11:06 AM: I am migrating from UW to dovecot and using mbox. I have been able to find Did you look at http://wiki.dovecot.org/Migration/UW ? -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't
Re: [Dovecot] Troubleshooting enhancement request...
Dovecot's -n actually works a bit differently. It lists only the settings that aren't the same as defaults, not the settings that have been uncommented in dovecot.conf. dovecot -d would be possible also, but I don't see it as that useful. Heh - I actually deleted a final comment something like 'or, maybe you could just make -n output based on actual diff from the known default settings for that version vs the current settings, not based on just the uncommented settings in the file' (the wording was awkward), so, you did it right from the beginning... Thanks! Also - did you see my earlier suggestion for adding to the output of -n? Sent on 4/26: I'm the one who suggested the '-n' option to capture the actual config settings that the running dovecot process was using (ala postfix), and you implemented it very quickly - so thanks for that! Now, I'd like to suggest an enhancement... Many people still do not provide basic things like dovecot version, and there are secondary config files like dovecot-ldap, whose settings are not included in the dovecot -n output. How difficult would it be to add these to the output so that the output would include the running dovecot version, as well as any extra config settings from any other files that are loaded when dovecot starts? It would sure make it easier, both for us troubleshooting on our own, and when asking for help on the list. Many thanks, and terrific job on 1.0! Now all dovecot lacks is full support for IMAP ACLs/shared folders, and support for single-instance storage, and it will have no real competition... -- Best regards, Charles
[Dovecot] Thunderbird or Dovecot bug? (multiple keywords)
Here's a strange one. I have a user who's using Thunderbird 2.0.0 and assigning multiple tags (keywords) to emails, which are getting lost (I'll explain) when he leaves the folder and comes back. I can reproduce this on *his* account myself, but cannot reproduce it on *my* account (separate new TBird 2.0.0 profiles on Windows XP). Use the two TBird default tags 'Important' and 'Work' for all these tests, which it refers to as $Label1 and $Label2 in IMAP-keywords land. If I go into my account, label an email with both tags, it sticks -- I can click on Drafts then back to Inbox, and both tags/keywords still show in the client. If I go into his account, add the two tags, then click on Drafts and back on Inbox, only the *second* tag (Work, $Label2) shows. If I remove that tag, then the first tag (Important, $Label1) immediately pops up! On the backend the actual Maildir files match the dovecot-keywords and have the correct letter appended in both cases - so, in his account when the email only shows one tag, the physical mail file has the letters for two tags. So Thunderbird should be showing both tags, like it does in my account where everything is working correctly. This leads me to believe that the problem has something to do with the difference of dovecot-keywords content, and the interaction TBird has with Dovecot. My account, working correctly, looks like: dovecot-keywords: 0 $Forwarded 1 $MDNSent 2 $Label2 3 $Label1 file: Maildir/cur/1178712608.H529732P11686.yak.fluid.com:2,RSdc ...which matches, d=$Label1 (Important), c=$Label2 (Work) and TBird is displaying the email as having both tags - all is well and good. Now, his account looks like: dovecot-keywords: 0 Junk 1 NonJunk 2 $Label4 3 $Label1 4 $Label2 5 $Label3 6 $Label5 file: Maildir/cur/1178728930.P28392Q0M960111.yak.fluid.com:2,RSbde ...again, everything matches on the server; yet, it Thunderbird is only displaying $Label2 (d,3). I also noticed something interesting, even if I have the TB 'Junk Controls' completely disabled on his account, and remove all tags using the menu option, that file still retains the 'b' (NonJunk) tag in the filename: Maildir/cur/1178728930.P28392Q0M960111.yak.fluid.com:2,RSb All this long-winded explanation leads me to believe that somehow the difference in dovecot-keywords is causing this problem, but what I can't tell is who's problem it is -- Dovecot, or Thunderbird? Thoughts welcome, -te PS: all the normal things tried like deleting the dovecot index files, Thunderbird cache files and profiles, etc. -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com
Re: [Dovecot] dovecot-dspam-integration
On Wed, 2007-05-09 at 16:09 +0200, Johannes Berg wrote: On Tue, 2007-05-08 at 04:06 -0600, Trever L. Adams wrote: I don't use --daemon right now, it was crashing too much and losing mail. YMMV. You have to limit the number of connections to 1. For some reason it locks up if there are more than 1. Well, you control how long the .sig files are kept around. I keep them a week longer than my spam folder contents. johannes How are you cleaning up the folder contents? Trever -- If destruction be our lot, we must ourselves be its author and finisher. As a nation of freemen, we must live through all time or die by suicide. -- Abraham Lincoln signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Email client dowloads previously read messages as new during migration.
Quoting Eric and Barbara Sammons [EMAIL PROTECTED]: I am migrating from UW to dovecot and using mbox. I did the same. I'm sure you'll be pleased by the results. I assume you are using 1.0 and not 0.99 versions? I have been able to find mbox to maildir migration information and tools; however, I have had little luck finding any tool or information for performing such a migration where I wish to keep mbox. ( I know I should migrate to MailDir, but in the case I wish to take baby steps.) There is nothing wrong with staying with mbox. There may be reasons it is best or better to do so (then again, there could be reasons to go to maildir instead -- it all depends on your needs and setup). There are few pages about the migration because there is so little to do for it. I have setup dovecot pop3 communication and I go to my email client and everything works fine with the exception that all mail I have previously read (when using UW as my POP server) is downloaded again as NEW. Is there a way to prevent this from happening without setting my client to delete mail from server? Did you set up your UID format properly in dovecot.conf? It should be: pop3_uidl_format = %08Xv%08Xu Other than that, it should pretty much work from my experience... thank you! Not sure I helped any, but you're welcome in any case. -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
Re: [Dovecot] removing old emails
Ray, We do this, deleting spam filtered messages older than 21 days. We also delete the index's and let Dovecot re-generate them. Have had no problems with this method for 4 months. Regards __ Dean Manners -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ray Sent: Thursday, May 10, 2007 7:56 AM To: dovecot@dovecot.org Subject: [Dovecot] removing old emails Hello, I need to remove mail older than for example 30 days. Email is stored in maildir format. can I just use a cron job and shell script or will that mess up indexs? Thanks Ray
Re: [Dovecot] removing old emails
On Wednesday 09 May 2007 9:11 pm, Dean Manners wrote: Ray, We do this, deleting spam filtered messages older than 21 days. We also delete the index's and let Dovecot re-generate them. Have had no problems with this method for 4 months. Regards __ Dean Manners Thanks, I thought that should work, but it just seemed to easy... Ray -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ray Sent: Thursday, May 10, 2007 7:56 AM To: dovecot@dovecot.org Subject: [Dovecot] removing old emails Hello, I need to remove mail older than for example 30 days. Email is stored in maildir format. can I just use a cron job and shell script or will that mess up indexs? Thanks Ray
