I see the new versions were not compiled with --disable-many-domains. That looks like it was discussed in the list way back in 2011.
Back then, when that decision was made, there much have been a
convenient way to migrate from one db structure to the other?
Remo,
Yes, but there are complications to doing that. I have many
domains, many users, different quotas, aliases, etc.
The command you sent.
Hi Gary,--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.comDid you recall my email? I said create the domain on the new server, then run the shell to create every user with password then sync from old to new on all emails and you would have been set. The script may have been changed Eric will know more about that but how I migrate which is a little longer does not depend on the old mysql. I had issue in the past so I just do that my own way and no issues at all.
Remo
On Feb 20, 2024, at 09:20, Gary Bowling <g...@gbco.us> wrote:
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
hmm, looks like the db structure changed since my old install?? Is that correct?
I created a new test domain in vpopmail with vadddomain which worked, then added a new user to that dummy domain.
When I look at the db, it now has a vpopmail table that has the following structure.
mysql> select * from vpopmail;
+------------+-----------+------------------------------------+--------+--------+------------+--------------------------------------------+-----------------+-----------------+
| pw_name | pw_domain | pw_passwd | pw_uid | pw_gid | pw_gecos | pw_dir | pw_shell | pw_clear_passwd |
My old server has a separate table for every domain, then the structure for each domain has this structure.
select * from gbco_us;
+----------------+------------------------------------+--------+--------+---------------------+-----------------------------------------------+------------+------------------+
| pw_name | pw_passwd | pw_uid | pw_gid | pw_gecos | pw_dir | pw_shell | pw_clear_passwd |
+----------------+------------------------------------+--------+--------+---------------------+-----------------------------------------------+------------+------------------+
The difference being the field "pw_domain"
So I guess the new structure has all the domains in the same table? If it does, then I need to figure out how to migrate my old db to the new format.
Thanks, gb
On 2/20/2024 11:37 AM, Gary Bowling wrote:
Thanks Eric.
Continuing through the "migration" page. After going through everything moving configs and my database, then restarting. Toaststat says everything is ok.
So I tried a simple run of ~vpopmail/bin/vuserinfo g...@gbco.us just to query an account. I get this error
mysql: sql error[3]: Table 'vpopmail.vpopmail' doesn't exist
Logging into the db and checking, indeed I do not have a vpopmail.vpopmail table. I have all the domain tables, etc. So I went back to my old server (the one this email is coming from) and it also does not have a vpopmail.vpopmail table.
I'm sure it has something to do with how old my existing server is. But how do I resolve this?
Thanks, gb
On 2/20/2024 10:00 AM, Eric Broch wrote:
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.comIt's all good and there's nothing to do.
On 2/20/2024 7:11 AM, Gary Bowling wrote:
Another question on my migration. On the qmailtoaster.com site, under the RHEL9 derivative install heading. There is the qmail1.03-3.3.8 header and underneath it is a link for "patches applied"
I'm confused if that means. It implies that those patches are already applied and there is no need to do them. But the link takes you to the page for the patch like it's something we should apply.
I'm pretty sure it's all good and there is nothing to do, just wanted to make sure.
Thanks, gb
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
