Matt Miller wrote:
> I'll look into the file tool; I'm unfamiliar with it.
It's pretty simple, and frequently useful:
$ file /etc/courier/aliases.dat
/etc/courier/aliases.dat: GNU dbm 1.x or ndbm database, little endian
> I tried doing the export + import routine, but got the same Invalid
> Arg
I'll look into the file tool; I'm unfamiliar with it.
I tried doing the export + import routine, but got the same Invalid
Argument error on the import.
Was there anything meaningful in the strace I posted?
Gordon Messmer wrote:
Matt Miller wrote:
Also, we are using gdbm as the storage fo
Matt Miller wrote:
> Also, we are using gdbm as the storage format for files in /etc/courier-
What were you using before? The "file" tool can probably tell you what
format the dat files are.
> rebuilding them resolved the problem that I posted about previously.
> Is there a similar way to reb
Heh, sorry, I meant to include a link to the trace...
http://www.itfreedom.com/temp/mlm.trace
Also, we are using gdbm as the storage format for files in /etc/
courier- rebuilding them resolved the problem that I posted about
previously. Is there a similar way to rebuild whatever additional
Matt Miller wrote:
> the short of it is that I'm migrating from a CentOS 4.1 x86 server
> running Courier 0.58.0 to a new one running Cent 5.1 x64 and
> Courier 0.59.0 and am running into some minor problems.)
...
>
>> [EMAIL PROTECTED]:/
>> $ cmlm sub /home/vmail/lists/itfreedom.com/cust
I'm still working on getting everything migrated from an old Courier
server to a new one (I posted further details a week or so ago with a
different question, but the short of it is that I'm migrating from a
CentOS 4.1 x86 server running Courier 0.58.0 to a new one running Cent
5.1 x64 and
