Using encoding=latin1 is supported but is not future proof. Migrate your dbmail database to UTF8 if you can, and change the ENCODING value accordingly. If the database uses UTF8 it will be able to hold any kind of characterset you will ever receive.
Using default_msg_encoding=latin1 is perfectly valid. Use whatever is the dominant charset among your user population. Use whatever the Outlook users use that send email to your users. Jim McIver wrote: > Thx to all who helped me get MySql and DBMail to speak. > > In dbmail.conf switched: > #encoding = utf8 > encoding = latin1 > and > #default_msg_encoding = utf8 > default_msg_encoding = latin1 > > I could then get connected to create a user. > > I still wanted to use utf8, so I added below to my.cnf > [mysqld] > default-character-set = utf8 > character-set-server = utf8 > > Switched dbmail.conf back to utf8...no luck. > > Dropped the dbmail database and re-created it with the above setting > in my.cnf. > > Can now connect with utf8. > > mysql> show variables for dbmail still sayes: > > | character_set_client | latin1 | > | character_set_connection | latin1 | > | character_set_database | utf8 | > | character_set_results | latin1 | > | character_set_server | utf8 | > | character_set_system | utf8 | > > but it works. Before the 'character_set_database' was latin1. > > thx again....now onto the next part of instructions. > > -Jim McIver > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
