[Dbmail] DBMail not logging

Hi. I'm attempting to use DBMail along with OpenSMTPD as a containerized email solution. Each component runs as a single process in a Docker container without syslog. Ideally all logging is sent to stdout/stderr so the "docker logs" command, and indirectly journalctl on CoreOS, can read conta

[Dbmail] DBMail logging revisited

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. A couple months back, I posted about having issues with DBMail's LMTP server not logging. Since then, I ran into issues getting OpenSMTPD talking to it and thought it was at fault, but after an exchange on the OpenSMTPD listserve/issue tracker,

Re: [Dbmail] DBMail logging revisited

? Wondering if this is due to the Docker container not providing syslog? I'd hoped that starting with -v, which the help claims logs to STDOUT/STDERR, would circumvent this. Thanks. On 9/7/2014 12:10 PM, Nolan Darilek wrote: > Hello. > > A couple months back, I posted about having issues

[Dbmail] SQLite permissions issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wondering if this is a bug or expected behavior. If I start DBMail configured to use SQLite as root, without an existing database, and with effective_user set, the database gets created owned by root. My expectation is that DBMail would change the dat

[Dbmail] DBMail fails after first IMAP connection

So as of now DBMail appears to deliver mail, but I can't for the life of me log in. In particular, Thunderbird seems to make one initial connection on account setup, then absolutely fails in the future and I see nothing in the logs. I then tried telneting to my IMAP server. Whereas initially I get

Re: [Dbmail] DBMail fails after first IMAP connection

On 9/8/2014 9:32 AM, Reindl Harald wrote: > > in case of "I need to switch to something" why don't you avoid > .0 releases and just start with the old-stable 3.1.17 in case > you don't want to invest time in debugging? > So 3.2.0 is considered unstable? ___