Displaying 20 results from an estimated 5000 matches similar to: "v1.2.5 released"
2009 Sep 14
1
v1.1.19 released
http://dovecot.org/releases/1.1/dovecot-1.1.19.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.19.tar.gz.sig
This is hopefully the last v1.1.x release.
- file_set_size() was broken with OSes that didn't support
posix_fallocate() (almost everyone except Linux), causing all kinds
of index file errors.
- ldap: Fixed hang when >128 requests were sent at once.
- Fixed a crash in
2009 Sep 14
1
v1.1.19 released
http://dovecot.org/releases/1.1/dovecot-1.1.19.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.19.tar.gz.sig
This is hopefully the last v1.1.x release.
- file_set_size() was broken with OSes that didn't support
posix_fallocate() (almost everyone except Linux), causing all kinds
of index file errors.
- ldap: Fixed hang when >128 requests were sent at once.
- Fixed a crash in
2013 Aug 05
1
Corrupted mboxes with v2.2.4, posix_fallocate and GFS2
Hi,
on a clustered Dovecot server installation that was recently moved from a
shared GPFS filesystem to GFS2, occasional corruptions in the users'
INBOXes started appearing, where a new incoming message would be appended
directly after a block of NUL bytes, and be scanned by dovecot as being
glued to the preceding message.
I traced this to the file extension operation performed in
2009 Nov 10
1
v1.1.20 released
http://dovecot.org/releases/1.1/dovecot-1.1.20.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.20.tar.gz.sig
Hopefully one of the last v1.1 releases.
* Upgraded to Unicode 5.2.0
- Maildir: Fixed crash when using a lot of keywords.
- file_set_size() was broken with OSes that didn't support
posix_fallocate() (almost everyone except Linux), causing all kinds
of index file errors.
2009 Nov 10
1
v1.1.20 released
http://dovecot.org/releases/1.1/dovecot-1.1.20.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.20.tar.gz.sig
Hopefully one of the last v1.1 releases.
* Upgraded to Unicode 5.2.0
- Maildir: Fixed crash when using a lot of keywords.
- file_set_size() was broken with OSes that didn't support
posix_fallocate() (almost everyone except Linux), causing all kinds
of index file errors.
2005 Apr 02
4
1.0-test66
http://dovecot.org/test/
I've still lots of mails in my INBOX and in this list that I should be
looking into.. But here's a release that fixes at least some things.
Maybe I'll make another one tomorrow..
Most importantly keyword code was changed a lot. It's now faster and
less buggy. The keywords are also finally written into mbox, and keyword
changes in the mbox are picked up.
2009 Jul 30
3
AIX and posix_fallocate
Hi,
AIX's implementation of posix_fallocate is a little bit, let me say,
peculiar. Attached is a patch to "fix" (=work around) this.
Without you'll see this in the logs:
Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr):
posix_fallocate() failed: File exists
Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr):
file_set_size() failed with mbox file
2007 Oct 18
2
more problems with dovecot-1.1 beta3
Hi,
Thank you for pointing me about -xc99 flag, I have compiled and
installed dovecot inplace of version 1.0.5 without any special actions
on the upgrade. And after starting it immediately got in it's log file
messages like:
---
dovecot: Oct 16 23:10:18 Error: IMAP(seriv): file_set_size() failed with
index cache file
/var/spool/imap/seriv/.imap/.git-altlinux-ru/dovecot.index.cache:
Invalid
2009 Oct 01
2
Compile dovecot 1.2.5 with managesieve patch 0.11.9?
Hi,
is it possible to compile dovecot 1.2.5 with the managesieve patch
0.11.9 which is for dovecot 1.2.4 or is it better to wait if a new
managesieve patch is released? Maybe 1.2.5 will work too?
Thanks,
Seba
2009 Dec 23
1
Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed
Hi all,
after inserting another sieve-rule, I get the following backtrace on
deliver.
The mail gets delivered into the Mailbox, but as deliver does not exit
with 0, postfix bounces the mail.
The additional rule is the same as all others in my .dovecot-sieve:
> require ["fileinto", "include"];
>
> if header :contains ["From"]
2009 Oct 05
1
v1.2.6 released
http://dovecot.org/releases/1.2/dovecot-1.2.6.tar.gz
http://dovecot.org/releases/1.2/dovecot-1.2.6.tar.gz.sig
A couple of random things:
- I decided to start using "hg sign" to gpg sign all releases in
mercurial repository.
- v2.0.alpha1 will hopefully be released in a week or two.
Changes since 1.2.5:
* Upgraded to Unicode 5.2.0
+ Added authtest utility for doing passdb and
2009 Oct 05
1
v1.2.6 released
http://dovecot.org/releases/1.2/dovecot-1.2.6.tar.gz
http://dovecot.org/releases/1.2/dovecot-1.2.6.tar.gz.sig
A couple of random things:
- I decided to start using "hg sign" to gpg sign all releases in
mercurial repository.
- v2.0.alpha1 will hopefully be released in a week or two.
Changes since 1.2.5:
* Upgraded to Unicode 5.2.0
+ Added authtest utility for doing passdb and
2009 Sep 23
9
pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
I have been running Dovecot 1.2.5 since Sept 14. Beginning at about
03:28 on Sept 21 for no apparent (to me) reason and continuing through
the present, I am seeing log messages like the following and am
experiencing delays logging in.
Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating
login processes, slowing down for now
Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:
2009 Sep 10
4
ldap quota dovecot
hi,
I've used dovecot 1.1.16 but after upgrade to dovecot 1.2.4 per-user
ldap quotas stoped working. My configuration:
# 1.2.4: /etc/dovecot.conf
# OS: Linux 2.6.18-128.7.1.el5xen x86_64 CentOS release 5.3 (Final) ext3
protocols: imap imaps pop3 pop3s managesieve
listen(default): *, [::]
listen(imap): *, [::]
listen(pop3): *, [::]
listen(managesieve): *:20000
login_dir:
2005 Aug 18
3
1.0 alpha1 released
As promised a few days ago, 1.0.alpha1 release is now available from
Dovecot web page.
Changes since 1.0-test80 include only one mbox assert crashfix and
removed fsync() call when writing to transaction log, making it a bit
faster.
I changed the version number also since 1.0-tests to 1.0.alpha. I know
'-' is problematic to binary package builders, maybe the new versioning
is better?
2014 Jan 09
1
imap auto create mailbox: we're not in group 8(mail)
Dear List
Somehow I don't understand the intended work flow to have new mailboxes
auto created. On login of a new user with no mailbox, I get
2014-01-09 12:53:06 imap(tester): Error: user tester: Initialization
failed: Namespace '': mkdir(/var/mail/tester) failed: Permission denied
(euid=1016(tester) egid=1016(tester) missing +w perm: /var/mail, we're
not in group 8(mail), dir
2008 Sep 02
2
v1.1.3 released
http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz.sig
This fixes several mbox problems previous v1.1 releases have had.
* mail_max_userip_connections limit no longer applies to master user
logins.
+ login_log_format_elements: Added %k to show SSL protocol/cipher
information. Not included by default.
+ imap/pop3-proxy: If
2008 Sep 02
2
v1.1.3 released
http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz.sig
This fixes several mbox problems previous v1.1 releases have had.
* mail_max_userip_connections limit no longer applies to master user
logins.
+ login_log_format_elements: Added %k to show SSL protocol/cipher
information. Not included by default.
+ imap/pop3-proxy: If
2008 Sep 22
2
Test environment question
My production DC machine owns the mail filesystems and is running DC
V1.0.15 and mbox folder format.
I am looking to test V1.1.3 on another machine, which NFS mounts the
mail filesystems, but has its own local index FS.
I have made this test environment my default connection in TBird, and it
seems to work just fine. Also, I have made sure that my TBird client
isn't connecting to the
2008 Oct 05
2
v1.1.4 released
http://dovecot.org/releases/1.1/dovecot-1.1.4.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.4.tar.gz.sig
- SORT: Yet another assert-crashfix when renumbering index sort IDs.
- ACL plugin fixes: Negative rights were actually treated as positive
rights. 'k' right didn't prevent creating parent/child/child mailbox.
ACL groups weren't working.
- Maildir++ quota: Fixes to