|
From: Simon L. <si...@kl...> - 2011-10-12 07:58:06
|
On 12/10/11 01:02, Christian Boltz wrote: > Hello, > > Am Dienstag, 11. Oktober 2011 schrieb Simon Loewenthal: >> The database was exported using mysqldump --all-databases>backup.sql, >> and imported with mysql <backup.sql >> >> [SNIP] > Just curious: you say "roundcube database" - is this the same database > that is also used by postfix? Or a different one? I was confused. Roundcube gets data from IMAP session, and also creates some user preferences in the roundcube dB. Roundcube (in my case) can also update the spamassassin.userprefs dB. Postfixadmin did not write into the roundcube dB. Additional confused was because I forgot to add the IP address of the new server into my PC's /etc/hosts so the vhost was handled. Result was that I was http ing to the wrong server. Fun and games. This would have been far easier if I could have just picked up the existing server image and dump it onto the new server, but is not possible int this case :( [SNIP] >> Sounds like it accesses an out-of-date database. >> Check your config if you have the hostname or IP of the old server >> hardcoded somewhere so that it queries the database on the old server. >> >> Or you really have two separate databases (I never used roundcube, so I >> don't know if it needs something like that) and need to sync them >> somehow. If it worked on the old server, implement the same thing on the >> new one ;-) [SNIP] > $CONF[logging] enables logging of all modifications on mailboxes, > aliases etc. It's stored in the database (table "log") and available in > the "view log" page of PostfixAdmin. > > Just to be sure, also check your apache error log. > > > Regards, > > Christian Boltz Thank-you Christian. The problem was caused by the way I thoughtlessly exported the data into the new server. I forgot that I had exported all dBs on the old one including the .mysql dB, which I imported into the new server: Resulted in a confused dB. I realised this as I fell asleep last night. Many thanks, Simon. |
