Relative paths in 'mailman start -C' are broken

GNU Mailman 3.0.0b1+ (current bzr head).

http://packages.python.org/mailman/src/mailman/docs/START.html#running-mailman-3 talks about ./mailman.cfg being used as configuration (among others). This seems to be only partially true.

I put this mailman.cfg into /usr/local/mailman

---
[database]
class: mailman.database.postgresql.PostgreSQLDatabase
url: postgres://mailman:mailman@xxx/mailman

[shell]
use_ipython: yes

[mta]
incoming: mailman.mta.postfix.LMTP
outgoing: mailman.mta.deliver.deliver
lmtp_host: mailout.xxx
lmtp_port: 8024
smtp_host: mailout.xxx
smtp_port: 25

[runner.nntp]
start: no
---

and started bin/mailman start. The PostgreSQL database was initialized, bin/mailman status showed the correct configuration location. I could create lists and they were added in the SQL database. It would use ipython as shell. But it would still try to send mail through localhost, and it would still start the nntp runner. And LMTP would reject mails to the existing lists with "mailbox unavailable". So it seems the configuration was only used by the main process, but not by the runners.

Moving the configuration to a non-relative location fixed it.