A BUGNOTE has been added to this bug. ====================================================================== http://dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000114 ====================================================================== Reported By: seanc Assigned To: ====================================================================== Project: DBMail Bug ID: 114 Category: Database layer Reproducibility: always Severity: crash Priority: normal Status: new ====================================================================== Date Submitted: 02-Nov-04 21:35 CET Last Modified: 02-Nov-04 23:14 CET ====================================================================== Summary: Crash/core when unable to connect to PostgreSQL... Description: When firing up dbmail-imapd and dbmail-pop3d, both daemons exit/abort with a recursive malloc(3) call when they're unable to connect to the specified database. In my case, I used an empty name field in dbmail.conf. ======================================================================
---------------------------------------------------------------------- aaron - 02-Nov-04 22:58 CET ---------------------------------------------------------------------- Doesn't seem to be a problem with MySQL, but I don't know if I'm breaking my dbmail.conf in the same way your are... Could you post the offending sections of your dbmail.conf? ---------------------------------------------------------------------- seanc - 02-Nov-04 23:14 CET ---------------------------------------------------------------------- Everything in my config was default: [DBMAIL] host= # host for database, set to localhost if database is om sqlport= # if you want to use TCP/IP for connecting to the database, sqlsocket= # when using a local socket connection to the database, fill user=dbmail # user to connect as to database pass=pass # password for user to database db= # name of database [EMAIL PROTECTED] # postmaster's email address. TRACE_LEVEL=2 except for the above settings. Once I added the right line to db, everything worked correctly. Was a pain to track down though because the stack had been clobbered it looked like and I wasn't getting any messages. Can you try with PostgreSQL? Bug History Date Modified Username Field Change ====================================================================== 02-Nov-04 21:35seanc New Bug 02-Nov-04 22:58aaron Bugnote Added: 0000339 02-Nov-04 23:14seanc Bugnote Added: 0000340 ======================================================================
