similar to: 1.0-test12

http://dovecot.org/test/ - Added pop3_mails_keep_recent setting. Currently this only means that mails won't be moved from new/ to cur/ in maildir. More I/O friendly. - Fixed \Recent-flag handling and counters to work correctly with maildir. I think it's finally working right :) - mbox syncing fixes (but expunging still not implemented) - some other fixes.. Please try and report what

http://dovecot.procontrol.fi/test/ I should have released 0.99.10 already I think.. There's just two annoying problems that I think should be fixed first: - PAM: If user gives a wrong password, dovecot-auth process sleeps for two seconds, blocking everyone else who are trying to authenticate at the time. So using PAM isn't very good idea at the moment. - OpenSSL problems. Are they

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors

http://dovecot.org/test/ Should work again with maildir. - Some bugfixes to indexes (possibly fixing the still persisting maildir sync errrors?) - Enabled cache file again. If client asks about something that can be cached for future, it's done. There's currently no smart logic about when not to do it or when to cache more than was asked for future use. Currently nothing is ever

I am bringing more people onto Dovecot...and am beginning to see syslog error messages I've never seen before...what are they/are they critical? 1 =========================== > Jun 12 09:53:21 mercury mail:err|error dovecot: IMAP(gregory): Corrupted index c > ache file /var/dcndx/gregory/.imap/INBOX/dovecot.index.cache: indexid changed This has the same date stamp as the user's

http://dovecot.org/test/ Well, remember when I said: > Here you go, maildir syncing problems finally fixed (I hope). Well, > except there's this "new-dir-only syncing" optimization which I'm not > really sure if it works as it should. Just before I found the expunge bug in index, I was trying to fix the new-dir-only syncing because the code looked wrong. Then I

I tried to disable courier-pop3 today in favour of dovecot pop3. Prior to that I ran: find /home -maxdepth 1 -type d | xargs --replace /usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive --convert {} ( /home is hashed two levels deep: /home/a/a/aanton/Maildir/ ) After that, I got lots of errors like: Aug 9 13:02:40 postamt dovecot: IMAP(azenclu): Maildir

Helo List, Sorry I missed the rest of my email in my previous post. Please see below. I'm having an issue using the AND (&) operator evaluation in the code of my dialplan. The dial plan is coded to detect inbound DTMF digits from callers. key "1" is equivalent to "yes" and key "2" is equivalent to "no" in two diferent contexts in the dial plan.

Hi, I'd like to change the log levels of a few of the errors that Dovecot throws. Our servers throw errors at the console above the 'Error' level, and there are a few that I'd like to change to 'Warn' so that they don't do so. Has anyone out there attempted this and can give me a few pointers? Or is there a doc somewhere about how to do this? Thanks,

A new employee started today, when logging into his new mailbox this morning during a walk-through I got a nasty server error response in Thunderbird - something I never see, DC runs smooth as butter for us. Checking the server log I see this: == snip == dovecot: Jul 09 09:38:54 Error: IMAP(xxxxxxx): Maildir /home/x/xxxxxxx/Maildir sync: UIDVALIDITY changed (1183406107 -> 1183999134)

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. NFS may have been used. Panic: IMAP(user): file mail-index-sync-update.c: line 843 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index- >indexid || map->hdr.indexid == 0) Two different backtraces to this error are: 0 libSystem.B.dylib 0x00007fff87b775ea __kill + 10 1

As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read. If I switch back to test-59, it works normally. When switching back to test-59, with log_path = /var/log/dovelog dovelog shows: dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed

Hi - We tried to access a dovecot-0.99.10.7 IMAPS server with a Blackberry 7230. The Blackberry was on loan so we don't have much access to it for testing. We got the following in our logs: Jul 27 12:30:27 xserv imap-login: Login: testuser [xxx.xxx.xxx.xxx] Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for binary tree file /home/testuser/mail//.imap/INBOX/.imap.index.tree Jul 27

Hello All, I'm new to the list and I don't have much of experience with samba. I have a test setup on CentOS 7.8 with samba-4.10.4 and samba-vfs-glusterfs . When my client mounts the samba share via vers=1.0 , the user sees the share properly (uid,gid,mode are just like on gluster). When the share is mounted with vers=2.0 or not specified (anything higher) the files are owned by

Should I be concerned about these errors? imap(msun): Jun 13 13:21:38 Error: Error indexing mbox file /home/msun/mail/Deleted Messages: LF not found where expected imap(msun): Jun 13 13:39:08 Error: Corrupted binary tree for index /home/msun/mail/.imap/INBOX/.imap.index: lookup returned index outside range (1 >= 0) imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for binary tree file

Hi Timo and All, after upgrading to 2.1.2 i'm getting a lot of these messages: Error: Corrupted squat uidlist file XXXXXX wrong indexid I did not have them before. Ideas? Luca

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in

Although the specific behaviour that was reported has been fixed, bugs remain in Sweave's processing of comment lines when keep.source=TRUE This is in some senses a follow-up from earlier bugs. Hence the query -- what is the preferred procedure, to submit a new bug report? (Another option might be to add a comment to the web page for bug 14459.) Is there now a preference to submit via

https://bugs.freedesktop.org/show_bug.cgi?id=69827 Priority: medium Bug ID: 69827 Assignee: nouveau at lists.freedesktop.org Summary: Uneven, jerky mouse movement, increasing CPU usage QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jimoe at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have an iMac v10.6. I'd like to get it to connect to an old os/2 server, v4.5 fp3. Using smbutils on the iMac: $ smbutil -v view //sma-server1.sma.com smbutil: server connection failed: RPC struct is bad Can anyone suggest what changes may be made that will correct this error? Is it even possible? - -- James Moe moe dot james at