Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
On Mon, 16 Feb 2009 07:20:58 -0800 (PST) Harakiri wrote: > that seems correct - i cant verify the issue of the OP - i created a > transport map db in etch, and verified it in lenny postfix 2.5.x - i > didnt have the issue. > > Seems like the OP doesnt have a full lenny upgrade?! A new install o

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Harakiri
--- On Mon, 2/16/09, Wietse Venema wrote: > > There are plenty platforms where the on-disk format of > Berkeley DB > database files is stable across many operating system > releases. > > Wietse that seems correct - i cant verify the issue of the OP - i created a transport map db in e

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Victor Duchovni
On Mon, Feb 16, 2009 at 10:14:21AM -0500, Wietse Venema wrote: > > hash == berkly db? that would mean its a poor choice by postfix itself > > There are plenty platforms where the on-disk format of Berkeley DB > database files is stable across many operating system releases. And the only sensible

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Wietse Venema
Harakiri: > --- On Mon, 2/16/09, Ralf Hildebrandt wrote: > > > From: Ralf Hildebrandt > > Subject: Re: postmap changed between 2.3.8 and 2.5.5 > > To: postfix-users@postfix.org > > Date: Monday, February 16, 2009, 8:00 AM > > * richard lucassen : > >

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Ralf Hildebrandt
* Harakiri : > the default for postfix is this: > > default_database_type = hash > > hash == berkly db? that would mean its a poor choice by postfix itself Not if you compile it yourself :) -- Ralf Hildebrandt (ralf.hildebra...@charite.de) snick...@charite.de Postfix - Einrichtung, B

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Harakiri
--- On Mon, 2/16/09, Ralf Hildebrandt wrote: > From: Ralf Hildebrandt > Subject: Re: postmap changed between 2.3.8 and 2.5.5 > To: postfix-users@postfix.org > Date: Monday, February 16, 2009, 8:00 AM > * richard lucassen : > > > > So it's a Debian bug (maps nee

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
On Mon, 16 Feb 2009 14:00:25 +0100 Ralf Hildebrandt wrote: > > Ok, thnx! It's our famous Linux downward compatability :-( > > Not really, it's you poor choice of a maptype :) Duh! :) > But on the other hand it's really hard to predict the future. If the future was predictable, I would certai

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Ralf Hildebrandt
* richard lucassen : > > So it's a Debian bug (maps need to be rebuilt). Or you could use cdb > > instead. > > Ok, thnx! It's our famous Linux downward compatability :-( Not really, it's you poor choice of a maptype :) But on the other hand it's really hard to predict the future. -- Ralf Hild

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
On Mon, 16 Feb 2009 13:46:17 +0100 Ralf Hildebrandt wrote: > * richard lucassen : > > When creating a db with 2.3.8 (Debian Etch), I get an error when > > reading the db file with 2.5.5 (Debian Lenny): > > > > postmap -q example.com hash:/tmp/valid_senders1 > > postmap: fatal: open database /tmp

Re: postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread Ralf Hildebrandt
* richard lucassen : > When creating a db with 2.3.8 (Debian Etch), I get an error when reading > the db file with 2.5.5 (Debian Lenny): > > postmap -q example.com hash:/tmp/valid_senders1 > postmap: fatal: open database /tmp/valid_senders1.db: Invalid argument > > I have to explicitely build the

postmap changed between 2.3.8 and 2.5.5

2009-02-16 Thread richard lucassen
When creating a db with 2.3.8 (Debian Etch), I get an error when reading the db file with 2.5.5 (Debian Lenny): postmap -q example.com hash:/tmp/valid_senders1 postmap: fatal: open database /tmp/valid_senders1.db: Invalid argument I have to explicitely build the db with the 2.5.5. version. Has so