http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz.sig If you've had problems with getting errors about index files sometimes being corrupted, please try if this release fixes it. If you've reported any bugs that this release hasn't fixed, please report them again so I know they still didn't get fixed and that I didn't forget them. * IMAP: When trying to fetch an already expunged message, Dovecot used to just disconnect client. Now it instead replies with dummy NIL data. * Priority numbers in plugin names have changed. If you're installing from source, you should delete the existing plugin files before installing the new ones, otherwise you'll get errors. * Maildir: We're using rename() to move files from tmp/ to new/ now. See http://wiki.dovecot.org/MailboxFormat/Maildir -> "Issues with the specification" for reasoning why this is safe. This makes saving mails faster, and also makes Dovecot usable with Mac OS X's HFS+ (after you also set dotlock_use_excl=yes, see below). + Added dotlock_use_excl setting. If enabled, dotlocks are created directly using O_EXCL flag, instead of by creating a temporary file which is hardlinked. O_EXCL is faster, but may not work with NFS. + If Dovecot crashes with Linux or Solaris, it'll log a "Raw backtrace". It's worse than gdb's backtrace, but better than nothing. + Added maildir_copy_preserve_filename=yes setting. + Added a lazy-expunge plugin to allow users to unexpunge their mails. + maildir quota: Added ignore setting to maildir quota, which allows ignoring quota in Trash mailbox. + dict quota: If dictionary doesn't yet contain the quota, calculate it by going through all the mails in all the mailboxes. + login_log_format_elements: Added %a=local port and %b=remote port + Added -i and -o options to rawlog to restrict logging only to input or output. - Doing a STATUS command for a selected mailbox (not a recommended IMAP client behavior) caused Dovecot to sync the mailbox silently. This could have lost eg. EXPUNGE events from clients, causing them to use wrong sequence numbers. - deliver was treating boolean settings set to "no" as if they were "yes" (they were supposed to be commented out for "no") - Running "dovecot" with -a or -n option while Dovecot was running deleted all authentication sockets, which caused all the future logins to fail. - maildir: RENAME and DELETE didn't touch control directory if it was different from maildir or index dir. - We treated internal userdb lookup errors as "user unknown" errors. In such situations this caused deliver to think the user didn't exist and the mail get bounced. - pam: Setting cache_key crashed - shared maildir: dovecot-keywords file's mode wasn't taken from dovecot-shared file. - dovecotpw wasn't working with PowerPC -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20070105/081c3951/attachment.pgp
Robert Schetterer
2007-Jan-05 17:02 UTC
[Dovecot] 1.0.rc16 released spec suse file not longer working
Hi Timo,
i used a spec file from suse for compile the rpm,
this worked since rc7 to rc15
now it fails, seems that number of plugins
is failure
as i read your changelog , but i have no idea how to fix this
do you have any idea?
failure is
RPM build errors:
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/lib01_quota_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/lib02_trash_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/lib01_convert_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/imap/lib01_convert_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/imap/lib01_zlib_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/imap/lib01_quota_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/imap/lib02_trash_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/imap/lib02_imap_quota_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/lda/lib01_convert_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/lda/lib01_quota_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/lda/lib02_trash_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/pop3/lib01_convert_plugin.so
File not found:
/var/tmp/dovecot-1.0.rc16-build/usr/lib64/dovecot/modules/pop3/lib01_quota_plugin.so
spec
--with-moduledir=%{_libdir}/%{pkg_name}/modules
perhaps someone on the list knows more about specs
Best Regards
Timo Sirainen schrieb:> http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz
> http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz.sig
>
> If you've had problems with getting errors about index files sometimes
> being corrupted, please try if this release fixes it. If you've
reported
> any bugs that this release hasn't fixed, please report them again so I
> know they still didn't get fixed and that I didn't forget them.
>
> * IMAP: When trying to fetch an already expunged message, Dovecot used
> to just disconnect client. Now it instead replies with dummy NIL
> data.
> * Priority numbers in plugin names have changed. If you're
installing
> from source, you should delete the existing plugin files before
> installing the new ones, otherwise you'll get errors.
> * Maildir: We're using rename() to move files from tmp/ to new/
now.
> See http://wiki.dovecot.org/MailboxFormat/Maildir -> "Issues
with
> the specification" for reasoning why this is safe. This makes
saving
> mails faster, and also makes Dovecot usable with Mac OS X's HFS+
> (after you also set dotlock_use_excl=yes, see below).
>
> + Added dotlock_use_excl setting. If enabled, dotlocks are created
> directly using O_EXCL flag, instead of by creating a temporary file
> which is hardlinked. O_EXCL is faster, but may not work with NFS.
> + If Dovecot crashes with Linux or Solaris, it'll log a
> "Raw backtrace". It's worse than gdb's backtrace,
but better than
> nothing.
> + Added maildir_copy_preserve_filename=yes setting.
> + Added a lazy-expunge plugin to allow users to unexpunge their mails.
> + maildir quota: Added ignore setting to maildir quota, which allows
> ignoring quota in Trash mailbox.
> + dict quota: If dictionary doesn't yet contain the quota,
calculate
> it by going through all the mails in all the mailboxes.
> + login_log_format_elements: Added %a=local port and %b=remote port
> + Added -i and -o options to rawlog to restrict logging only to
> input or output.
> - Doing a STATUS command for a selected mailbox (not a recommended
> IMAP client behavior) caused Dovecot to sync the mailbox silently.
> This could have lost eg. EXPUNGE events from clients, causing them
> to use wrong sequence numbers.
> - deliver was treating boolean settings set to "no" as if
they were
> "yes" (they were supposed to be commented out for
"no")
> - Running "dovecot" with -a or -n option while Dovecot was
running
> deleted all authentication sockets, which caused all the future
> logins to fail.
> - maildir: RENAME and DELETE didn't touch control directory if it
was
> different from maildir or index dir.
> - We treated internal userdb lookup errors as "user unknown"
errors.
> In such situations this caused deliver to think the user didn't
> exist and the mail get bounced.
> - pam: Setting cache_key crashed
> - shared maildir: dovecot-keywords file's mode wasn't taken
from
> dovecot-shared file.
> - dovecotpw wasn't working with PowerPC
>
--
Diese Nachricht wurde auf Viren und andere gef?hrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
Hi Timo, I see that you didnt fix the encoded subject issue. Does that mean you dont see it as a bug? The issue is that encoded subjects (and possibly other headers) get sorted wrong. They get sorted as their encoded string instead of whatever data was encoded. Im not quite sure of the standards surrounding this problem. Maybe the customers I have that are seeing this issue (which I can reproduce) are just doing something that isnt allowed. If you feel that's the case I can at least tell them to stop encoding :) Cor
At 5:46 PM +0200 1/5/07, Timo Sirainen wrote:>http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz >http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz.sig > >If you've had problems with getting errors about index files >sometimes being corrupted, please try if this release fixes it. If >you've reported any bugs that this release hasn't fixed, please >report them again so I know they still didn't get fixed and that I >didn't forget them.[...]> * Maildir: We're using rename() to move files from tmp/ to new/ now. > See http://wiki.dovecot.org/MailboxFormat/Maildir -> "Issues with > the specification" for reasoning why this is safe. This makes saving > mails faster, and also makes Dovecot usable with Mac OS X's HFS+ > (after you also set dotlock_use_excl=yes, see below). > > + Added dotlock_use_excl setting. If enabled, dotlocks are created > directly using O_EXCL flag, instead of by creating a temporary file > which is hardlinked. O_EXCL is faster, but may not work with NFS.Can you expand on this? I have been running Dovecot on a MacOS 10.4 PPC machine with Maildir on local (HFS+) disk for some time and have had intermittent and hard-to-characterize problems that manifest themselves as clients (Eudora, Palm VersaMail, and Outlook) timing out and hanging as one tries to move messages between mailboxes in the same account. The cargo-cult approach I've used to eliminate the hangs has been unsatisfying (cycle all clients and Dovecot, remove index files and temp files in mailbox directories) but even with rawlogging I have been unable to nail down the source of the trouble definitively. It looks like maybe bad index files or maybe some sort of locking issue, but the logs don't show anything other than the clients timing out and dropping connections. I don't understand the description of those rc16 changes because it seems like dotlocking would be irrelevant for Maildir anyway. Should I set dotlock_use_excl=yes even though I'm using fcntl? -- Bill Cole bill at scconsult.com