Thanks for the clarification on the setup issue it makes sense. The actual problem was just postfix not being installed on my system. I'll update the doc issue accordingly and remove the NullMTA mention.
On the hack comment after looking at the code,i noticed _get_preferences() in UserMailmanSettingsView calls preferences.save() on every GET request after merging system defaults with user preferences. So just visiting the preferences page can silently convert an "unset" preference into an explicitly set one, which breaks the inheritance chain. Would the right fix be to only display the combined values on GET without saving, and only persist when the user actually submits the form? Also, should I open a separate issue for this or is it considered part of the User Profile Tool scope? On the User Profile Tool — my current understanding is a unified view presenting preferences across all scopes with source tracking, so users can see where each effective value is coming from. I'm going through the existing code before drafting a proposal and will share a draft for feedback once I have a clearer picture. Regards, Rushikesh Bathe _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
