On 10/17/24 13:41, Andy Matthews wrote:
and then rebuilt kubernetes, I found that when I hit the API to get all lists, the list mailman@foobar.com existed, and was the default. I could create lists against foobar.com but could no longer create them against mydomain.com.
So it looks like when you're initially configuring mailman you have to create your first mailing list, and whatever domain you use becomes your "primary domain". I don't know where this is documented, but could someone confirm this behavior for me so that I know that I'm on the right path?
And previously you wrote:
- Shell into the mailman server
- Shell into the mailman Python environment: mailman shell
- Add a new mailing list. from mailman.interfaces.domain import IDomainManager from zope.component import getUtility manager = getUtility(IDomainManager) manager.add('testing.com') show_domains() # with method from the above documentation URL <Domain testing.com> <Domain mydomain.com>
Did you commit() after doing the above?
I'm not sure how kubernetes fits in to this, but mailman create for a
list in an unknown domain will create the domain unless -D or
--no-domain is specified. See mailman create --help.
Mailman core has no concept of primary domain which is why it's not
documented.
Are you creating lists via REST as you posted previously. If so, the domain must exist, but if you created domains as above, they should exist as long as you committed your changes.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan