On Sun, 3 Mar 2019 at 08:29, Voytek Eymont via dovecot <dovecot@dovecot.org>
wrote:
>
> > 11:30:12 auth-worker(32307): Warning: sqlpool(mysql): Query failed,
> > retrying: Unknown column 'mailbox.enableimaptls' in 'where clause'
> > Mar 03 11:30:12 auth-worker(32307): Error:
> > sql(voy...@sbt.net.au,110.175.246.167,<xBk6viWDzrRur/an>): User query
> > failed: Unknown column 'mailbox.enableimaptls' in 'where clause'
>
> I've found a page with SQL table mods that seems to have fixed some of my
> issues, after modifying SQL, I can log in
>
> Mar 03 16:23:34 master: Info: Dovecot v2.3.4.1 (3c0b8769e) starting up for
> pop3,
> imap, sieve (core dumps disabled)
> Mar 03 16:23:56 config: Warning: please set ssl_dh=</etc/dovecot/dh.pem
> Mar 03 16:23:56 config: Warning: You can generate it with: dd
> if=/var/lib/doveco
> t/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der >
> /etc/dovecot/d
> h.pem
> Mar 03 16:23:57 imap-login: Info: Login: user=<voy...@sbt.net.au>,
> method=PLAIN,
> rip=110.175.246.167, lip=103.106.168.106, mpid=2757, TLS,
> session=<283B2CmDccdu
> r/an>
>
> I'll do the dh.pem next
>
> //these are SQL mods I've done
>
> ALTER TABLE mailbox ADD COLUMN enableimaptls TINYINT(1) NOT NULL DEFAULT 1;
> ALTER TABLE mailbox ADD INDEX (enableimaptls);
> ALTER TABLE mailbox ADD COLUMN enablepop3tls TINYINT(1) NOT NULL DEFAULT 1;
> ALTER TABLE mailbox ADD INDEX (enablepop3tls);
> ALTER TABLE mailbox ADD COLUMN enablesievetls TINYINT(1) NOT NULL DEFAULT
> 1;
> ALTER TABLE mailbox ADD INDEX (enablesievetls);//
>
> --
> Voytek
>
>
What you did is quite practical. All you have to do is:
1. Make sure the static files named in the configs are moved to the
destination server
2. All account names used in Dovecot config are adjusted or created in the
destination server
and the permissions/access levels are right
3. Dump mysql database and import the dump in the destination server
I have done the same before, and just made sure that I went through all the
files in /etc/dovecot/ with
a toothcomb. I've missed one or two things depending on the level of
distraction/concentration (which is
normal), but it always ends up working, especially if the migration is
about the same domain names.
That is how it's supposed to work with virtual users I suppose.
Regarding your MySQL issues, you'll notice that we all have different MySQL
schemas out here, Unless
the one you refer to is the standard one for CentOS, every man to their own
when it comes to virtual users :)
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
