On Fri, 14 Sep 2007, Rudy Gevaert wrote:
Should I worry? It seems to me I should.
No. The effect is entirely cosmetic, other than the fact it was causing my
sanity check scripts (make_md5 is actually bundled with Cyrus) to freak.
Some MUAs, such as PINE will display the lcase()ed ENVELOPE
Eventually worked out that if a message is delivered by LMTP to several
recipients, then the first recipient gets a correct ENVELOPE, but all the
following recipients get an lcase()ed version. The reason is that
append_fromstage() in 2.3 reuses the "struct body" calculated for the
first recip
David Carter wrote:
Both at:
http://www-uxsup.csx.cam.ac.uk/~dpc22/cyrus/patches/2.3cvs/
write_searchaddr.patch
==
Spend some time this afternoon working out why the make_md5 databases on
my shiny new Cyrus 2.3 mailstores were going nuts: "Cache Mismatch".
Eventually w
On Thu, 13 Sep 2007, Ken Murchison wrote:
2) message_parsed_mapped_async() is an historical anomaly.
It should really be replaced by message_parse_body() and
message_create_record(). The existing parameters aren't quite right.
How about the attached patch as a replacement for
message_p
David Carter wrote:
message_parsed_mapped_async.patch
=
Trivial patch, long blurb. Will not affect other Cyrus deployments.
content_lines and cache_version were not being passed correctly.
Slightly embarrassed since I sent in a fix for the parent routine a few
Both at:
http://www-uxsup.csx.cam.ac.uk/~dpc22/cyrus/patches/2.3cvs/
write_searchaddr.patch
==
Spend some time this afternoon working out why the make_md5 databases on
my shiny new Cyrus 2.3 mailstores were going nuts: "Cache Mismatch".
Eventually worked out that if a m
