[Bug 982551] [NEW] ./mailman.cfg only used partially

Bernhard Schmidt berni at birkenwald.de
Sun Apr 15 21:45:35 CEST 2012

Public bug reported:

GNU Mailman 3.0.0b1+ (current bzr head).

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

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

use_ipython: yes

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

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.

** Affects: mailman
     Importance: Undecided
         Status: New

You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

  ./mailman.cfg only used partially

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list