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 db with the 2.5.5. version. Has
> something changed or is it a bug?

That's normal since the old and the new version of Postfix in Debian
use incompatible BerkeleyDB versions which generate incompatible on
disk formats.

So it's a Debian bug (maps need to be rebuilt). Or you could use cdb
instead.

-- 
Ralf Hildebrandt (ralf.hildebra...@charite.de)  snick...@charite.de
Postfix - Einrichtung, Betrieb und Wartung   Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
Nichts kann ohne Einsamkeit entstehen.

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/valid_senders1.db: Invalid
> > argument
> > 
> > I have to explicitely build the db with the 2.5.5. version. Has
> > something changed or is it a bug?
> 
> That's normal since the old and the new version of Postfix in Debian
> use incompatible BerkeleyDB versions which generate incompatible on
> disk formats.
> 
> 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 :-( 


-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+

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 Hildebrandt (ralf.hildebra...@charite.de)  snick...@charite.de
Postfix - Einrichtung, Betrieb und Wartung   Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
The Website you seek
Cannot be located, but
Countless more exist.

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 certainly live on the Bahama's
now :)

Btw: when building an old hash type db version, it can be read it with a
cidr query. Anyway, I'll find a workaround for the time being. Thnx for
your reply!

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+

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 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.


the default for postfix is this:

default_database_type = hash

hash == berkly db? that would mean its a poor choice by postfix itself

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, Betrieb und Wartung   Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
Ah, young webmaster... java leads to shockwave. Shockwave leads to
realaudio. And realaudio leads to suffering.

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 :
> > 
> > > > 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.
> 
> 
> the default for postfix is this:
> 
> default_database_type = hash
> 
> 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.

Wietse

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 default database type is one for which the libraries
are included with the base platform. CDB is not nearly as ubiquitous as
Berkeley DB. The choice of Berkeley DB is not "poor", even if the file
format changes periodically. When you upgrade your O/S, be prepared to
rebuild indexed tables.

-- 
Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:


If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

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 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?!

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 of Lenny. Lenny reads files that were made by Etch, but
not the other way round. So there still is a bit downward compatibilty
;-)

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+