On Fri, May 11, 2007, Jim McIver <[EMAIL PROTECTED]> said: > Aaron, > I probably just need to uncomment the lines in /etc/my.cnf, correct? > ie.. > #innodb_data_home_dir = /var/lib/mysql/ > #innodb_data_file_path = ibdata1:10M:autoextend > #innodb_log_group_home_dir = /var/lib/mysql/ > #innodb_log_arch_dir = /var/lib/mysql/ > # You can set .._buffer_pool_size up to 50 - 80 % > # of RAM but beware of setting memory usage too high > #innodb_buffer_pool_size = 16M > #innodb_additional_mem_pool_size = 2M > # Set .._log_file_size to 25 % of buffer pool size > #innodb_log_file_size = 5M > #innodb_log_buffer_size = 8M > #innodb_flush_log_at_trx_commit = 1 > #innodb_lock_wait_timeout = 50
These are for performance tuning. The defaults are fine for most people. > I also found a link about someone switching from MyIsam to innodb and > running a bunch of alter table commands. I can probably ignore these, > correct? > > myslq> alter table dbmail_users type=innodb > etc.. Because the tables are already innodb ;-) > When I do: > mysql> show variables; it looks like everything is set to latin1, so > I'm going to have change all of these, correct? > character_set_client latin1 > character_set_connection latin1 > character_set_database latin1 > character_set_results latin1 > thx, > -jm These have to match the values in dbmail.conf. Both sides are configurable, pick one and run with it. I suggest setting MySQL to run in utf8, because they're moving in that direction and default MySQL installations are starting to show up in utf8 mode now. If you have other database apps that expect latin1, then you'll need to be more careful about global changes to MySQL. >From dbmail.conf: # # encoding must match the database/table encoding. # i.e. latin1, utf8 encoding = utf8 # # messages with unknown encoding will be assumed to have # default_msg_encoding # i.e. iso8859-1, utf8 default_msg_encoding = utf8 Aaron > On 11 May 2007 at 0:22, Aaron Stone wrote: > >> It doesn't exist... oh, looks like we forgot to remove references to it in >> the documentation! There's now only one create_tables.mysql and it >> requires InnoDB tables. Don't worry, you've got the right tables already. >> The issue is your encoding. >> >> If you bump up the trace level to 5, the dbmail logs will give you lots >> more information about the encodings it expects and what the server is >> reporting. >> >> Aaron >> >> On Thu, May 10, 2007, Jim McIver <[EMAIL PROTECTED]> said: >> >> > Any idea where I can get the "create_tables_innoDB.mysql" script? >> > thx, >> > -jm >> > >> > On 10 May 2007 at 23:42, Jorge Bastos wrote: >> > >> >> You see InnoDB because your mysql has InnoDB enabled and so, it starts it. >> >> And to use dbmail 2.2x you NEED to use InnoDB >> >> >> >> >> >> ----- Original Message ----- >> >> From: "Jim McIver" <[EMAIL PROTECTED]> >> >> To: <[email protected]> >> >> Sent: Thursday, May 10, 2007 10:36 PM >> >> Subject: [Dbmail] postfix, mysql >> >> >> >> >> >> > I'm a newbie looking for a program to store email from postfix. >> >> > >> >> > I downloaded dbmail-2.2.4.tar.gz and followed along the instructions >> >> > in INSTALL. >> >> > >> >> > I don't know how to obtain innodb for mysql, so I ran the other >> >> > script. >> >> > >> >> > cp dbmail.conf to /etc >> >> > driver = mysql >> >> > authdriver = sql >> >> > host = localhost >> >> > sqlport = 3306 >> >> > sqlsocket = /var/lib/mysql/mysql.sock >> >> > user = dbmail >> >> > pass = dbmail >> >> > db = dbmail >> >> > >> >> > left everything else default. >> >> > >> >> > Ran configure --with -mysql >> >> > Ran make all & make install....no errors. >> >> > >> >> > Ran dbmail-users -a james -w james -g 0 -m 0 -s [EMAIL PROTECTED] >> >> > bignickel.com >> >> > >> >> > and get "Error collation mismatch, your MySQL configuration specifies >> >> > a different charset than the data currently in your DBMail database. >> >> > Failed. Could not connect to database (check log)" >> >> > >> >> > mysqld.log has this: >> >> > 070510 14:08:24 mysqld started >> >> > 070510 14:08:24 InnoDB: Started; log sequence number 0 167715 >> >> > 070510 14:08:24 [Note] /usr/sbin/mysqld: ready for connections. >> >> > Version: '5.0.18' socket: '/var/lib/mysql/mysql.sock' port: 3306 >> >> > SUSE MySQL RPM >> >> > >> >> > Not sure why I see InnoDB? >> >> > and >> >> > logfile = /var/log/dbmail.log >> >> > but there is no dbmail.log? >> >> > >> >> > Any thoughts? >> >> > thx, >> >> > >> >> > >> >> > -Jim McIver >> >> > >> >> > _______________________________________________ >> >> > DBmail mailing list >> >> > [email protected] >> >> > https://mailman.fastxs.nl/mailman/listinfo/dbmail >> >> > >> >> _______________________________________________ >> >> DBmail mailing list >> >> [email protected] >> >> https://mailman.fastxs.nl/mailman/listinfo/dbmail >> > >> > >> > >> > -Jim McIver >> > >> > _______________________________________________ >> > DBmail mailing list >> > [email protected] >> > https://mailman.fastxs.nl/mailman/listinfo/dbmail >> > >> >> -- >> >> >> >> _______________________________________________ >> DBmail mailing list >> [email protected] >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > > -Jim McIver > > -- _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
