[dovecot/core] fed9f7: doveadm: Do not use INT64 with mail cmds yet
GitHub
noreply at github.com
Wed Jun 1 09:30:12 UTC 2016
Branch: refs/heads/master
Home: https://github.com/dovecot/core
Commit: fed9f797a9d7647f78eeec3fcea91972ed45bbbe
https://github.com/dovecot/core/commit/fed9f797a9d7647f78eeec3fcea91972ed45bbbe
Author: Aki Tuomi <aki.tuomi at dovecot.fi>
Date: 2016-06-01 (Wed, 01 Jun 2016)
Changed paths:
M src/doveadm/doveadm-mail-index.c
M src/doveadm/doveadm-mail-mailbox.c
Log Message:
-----------
doveadm: Do not use INT64 with mail cmds yet
Commit: 9625595c47c665f5aee57ebfcb1fcbe9ad1bf3a0
https://github.com/dovecot/core/commit/9625595c47c665f5aee57ebfcb1fcbe9ad1bf3a0
Author: Martti Rannanjärvi <martti.rannanjarvi at dovecot.fi>
Date: 2016-06-01 (Wed, 01 Jun 2016)
Changed paths:
M src/auth/mech-rpa.c
M src/auth/passdb.c
M src/auth/passdb.h
M src/auth/userdb.c
M src/auth/userdb.h
M src/lib-storage/index/mbox/mbox-md5-all.c
M src/lib-storage/index/mbox/mbox-md5-apop3d.c
M src/lib-storage/index/mbox/mbox-md5.h
M src/lib/guid.c
M src/lib/guid.h
M src/lib/macros.h
M src/lib/md4.c
M src/lib/md4.h
M src/lib/md5.c
M src/lib/md5.h
M src/lib/sha1.c
M src/lib/sha1.h
M src/lib/sha2.c
M src/lib/sha2.h
M src/plugins/pop3-migration/pop3-migration-plugin.c
M src/plugins/pop3-migration/pop3-migration-plugin.h
Log Message:
-----------
[LEN] to [static LEN] on some function parameters
Also add STATIC_ARRAY macro to hide it in c++ compilation.
Commit: 04f9886078d53b136f747484b3ad9e1f7fad5994
https://github.com/dovecot/core/commit/04f9886078d53b136f747484b3ad9e1f7fad5994
Author: Timo Sirainen <timo.sirainen at dovecot.fi>
Date: 2016-06-01 (Wed, 01 Jun 2016)
Changed paths:
M src/lib/istream-chain.c
Log Message:
-----------
lib: Fixed max_buffer_size handling in istream-chain
The default max_buffer_size=256 was wrong in all situations.
We're now assuming that the underlying istreams' max_buffer_size is always
correct. While gluing together two streams we're now allocating enough
memory to hold all of the wanted data (instead of assert-crashing as could
have happened earlier). This means that the max memory usage is actually
the two streams' max_buffer_size summed together. Ideally this would be
fixed to limit the max_buffer_size to maximum of the two, but that would
require further changes.
Commit: 38b9e0b1982c310295b013b2253cc9421f9ed385
https://github.com/dovecot/core/commit/38b9e0b1982c310295b013b2253cc9421f9ed385
Author: Timo Sirainen <timo.sirainen at dovecot.fi>
Date: 2016-06-01 (Wed, 01 Jun 2016)
Changed paths:
M src/lib-fs/fs-metawrap.c
M src/lib-fs/istream-metawrap.c
Log Message:
-----------
fs-metawrap: Fixed buffer size while reading metadata header.
It's not enough to have the buffer size set to "large enough" at the time of
the stream creation, because i_stream_set_max_buffer_size() could be called
afterwards.
Compare: https://github.com/dovecot/core/compare/b90dc2ae3d65...38b9e0b1982c
More information about the dovecot-cvs
mailing list