Paul, Thanks for you help on this...
----- Original Message -----
From: "Paul J Stevens" <email@example.com>
To: "DBMail mailinglist" <firstname.lastname@example.org>
Sent: Sunday, May 16, 2010 9:14:20 AM GMT -05:00 US/Canada Eastern
Subject: Re: [Dbmail] FATAL: database "dbmail" does not exist? - and no dbmail logs
Lou Picciano wrote: > Hello dbmailers!
> Am attempting setup of a new installation of dbmail - using
> We do have a backend database set up, called 'dbmail' and Postfix is
> apparently trying to connect, but is saying 'connect to pgsql server
> localhost: FATAL: database "dbmail" does not exist?'
SOLVED: This was my late-night testing-while-exhausted error: my mistake! I had been testing incorrect syntax
for passing a non-standard database port to the dbmail connection. I was, however, ultimately able to connect to the database with a syntax of hostname:port > Note: we can connect correctly using same login details using psql, so
> don't think this is the problem.
How sure are you? Please share some details like the relevant parts of
your dbmail.conf and the command-line test you use. > Also, both queries in the sql interface files return 0 results, as they
> should, right?
Both queries? What queries are those?
The two queries, of course, put into files as suggested by the Wiki's documentation on postgresql setup_postfix:
sql-virtual_mailbox_domains.cf sql-virtual_mailbox_maps.cf > Last, I cannot get dbmail to write to either of its logs.
Not even syslog??? Makes me wonder if you are 1) running the binaries
you think you are running, 2) using the dbmail.conf file you think
dbmail is using.... You wouldn't be the first :-)
Fair enough, but am using the location of /etc/dbmail.conf, as suggested by docs. (Is there a way to direct
No, our logs for various services have been segregated - syslog is empty.
Also, we are not running the dbmail-impad binary at all yet... > Clearly, we're getting close - can someone suggest something? Thanks, Lou
Yes, send us your trace_syslog=5 logs. Oh wait, no logs you say.
Try 'dbmail-imapd -n -f /etc/dbmail/dbmail.conf' with dbmail.conf
Ah, hah! Your note suggests the resolution here. Is it that only specific daemons which write to the log? We haven't yet even used dbmail-imapd yet, for example, but I would have assumed we are engaging dbmail-lmtp, no? For the moment, we are testing only the 'inbound' trunk Postfix->PostgreSQL(dbmail) - trying to test one thing at a time. So, I'm guessing: we are not yet engaging any dbmail-log-writing daemons yet. Correct?
Also, we've been referencing documentation which states that configuration belongs in /etc/dbmail.conf. Is this incorrect?
Is /etc/dbmail/dbmail.conf the correct location? Is there an option to have a dbmail binary regurgitate its expected configuration location (as long as we're having it spill its guts??!!) I've since checked; apparently not.
That should make dbmail spill it's guts on stderr.
That command was very helpful, indicating a successful startup: dbmail imap (protocol version 4r1) server 2.2.15 ready to run. We used both 'dbmail-imapd -n -f /etc/dbmail.conf' and ; the two commands seem equivalent. But log output suggests some other things to fix - again, though, impad is not our immediate priority:
no value for SOCKET in config file
no value for BACKLOG in config file. Using default value 
...Still nothing being written to dbmail.err or dbmail.log. >
> DBmail mailing list
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
DBmail mailing list