Mailing List Archive: [PATCH] exim-4.04 support non-HASH db files

This is a multi-part message in MIME format.
--
Well, I found the problem I was having doing a db lookup into a Cyrus IMAPD
mailboxes.db file... Cyrus uses BTREE-style files, and Exim uses only
HASH-style files, and assumes that's all you'd ever want to look into.

The attached patch modifies the behavior of exim-4.04 (only for when db3 is
in use) to allow the file to be any format if it's being opened in read-only
mode, but specify DB_HASH if it's not (like when exim is actually creating a
new db file). This works great for me, exim has no trouble reading
previously created exim db files, but now can also read Cyrus db files.
--
[ exim-dblookup-patch of type application/octet-stream deleted ]
--

On Thu, 6 Jun 2002, Kevin P. Fleming wrote:

> Well, I found the problem I was having doing a db lookup into a Cyrus IMAPD
> mailboxes.db file... Cyrus uses BTREE-style files, and Exim uses only
> HASH-style files, and assumes that's all you'd ever want to look into.

Aha! I'd never considered that possibility.

> The attached patch modifies the behavior of exim-4.04 (only for when db3 is
> in use) to allow the file to be any format if it's being opened in read-only
> mode, but specify DB_HASH if it's not (like when exim is actually creating a
> new db file). This works great for me, exim has no trouble reading
> previously created exim db files, but now can also read Cyrus db files.

Please send me the patch privately, and I'll take a look at it. It
didn't make it onto the mailing list, because you attached it rather
than including it inline.

> [ exim-dblookup-patch of type application/octet-stream deleted ]

--
Philip Hazel University of Cambridge Computing Service,
ph10@cus.cam.ac.uk Cambridge, England. Phone: +44 1223 334714.