Hi Paul et al, I changed the conf file to encoding=utf8, and it worked perfectly. This confuses me since that was of course the first thing I tried when I ran into this problem, and that didn't work! I must have spelled it wrong, or forgotten to start dbmail, or something else equally stupid...sigh.
My sincere apologies for wasting your time! Thanks again, Naomi On Nov 17, 2007 1:28 AM, Paul J Stevens <[EMAIL PROTECTED]> wrote: > Naomi, > > reading the logs I see: > > Nov 16 13:04:12 babybop dbmail/imap4d[3417]: Debug:[misc] > misc.c,dbmail_iconv_init(+2110): Initialize DB encoding surface > [UTF-8..iso-8859-1] > Nov 16 13:04:12 babybop dbmail/imap4d[3417]: Debug:[misc] > misc.c,dbmail_iconv_init(+2114): Initialize DB decoding surface > [iso-8859-1..UTF-8] > Nov 16 13:04:12 babybop dbmail/imap4d[3417]: Debug:[misc] > misc.c,dbmail_iconv_init(+2118): Initialize default MSG decoding surface > [iso-8859-1..UTF-8] > > This means you have specified in your dbmail.conf: > encoding=iso-8859-1 > default_msg_encoding=iso-8859-1 > > but: > > [ERROR: invalid byte sequence for encoding "UTF8": > > which means your database is in utf8. > > The encoding field in dbmail.conf *must* be the same as your database's > encoding - your default_msg_encoding is ok. > > please set encoding=utf8, restart imapd, and try again. If it fails > again, try sending *those* logs. > > > -- > ________________________________________________________________ > 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 >
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
