Craig Leres via Mailman-users writes:
I got a version of this to work but was not satisfied because it required hacking either mailman or sendmail config to cleanup the domain in the recipient address.
You're talking about the ".private" extension on the domain? I think you can just put that in the "alternate domain" attribute. Postfix sometimes requires a similar dummy domain, so it's documented in the Postfix section of mta.rst.
First, how does one build the mailman 3 documentation?
Thanks for stepping up on this! I imagine Sendmail configuration has been something of a pain point for *BSDs.
For Mailman core, "tox run -e docs". I suppose it's similar for other modules if there is a configuration for tox there. We would like to move away from tox, I think, but it's a huge amount of configuration, including a certain number of packages that need to be available to sphinx. And there's a lot of muscle memory built up now. ;-)
Next, how are code and documentation contributions submitted for consideration? I'm a lot more familiar with github than gitlab and know how to fork but it didn't look like I would be able to submit a pull request.
We ask that you write a NEWS item (docs/NEWS.rst), and include that in the MR. Add "(:mr:42)" at the end, for value of "42" = the merge request number assigned by GitLab. Just a one-liner saying docs for Sendmail configuration were added is fine.
Once you've forked from gitlab.com/mailman/mailman, in your own fork you find the "merge requests" item in the sidebar. That should take you to your merge requests. I gather from your question you have none yet, so you should see a empty page with a "create merge request" button in the middle.
GitLab has been experimenting with alternative UIs recently, so you may not see a sidebar, etc. If so, tell me what you do see, I'll try to help out.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan