Re: [Mailman-Developers] [MM3-users] Re: Mailman 3.1 beta coming soon
On 2016-12-12 12:29 AM, Stephen J. Turnbull wrote: Barry Warsaw writes: > >I can also work on Postorius. Also in this vein I have a question. > >Should the DMARC settings be added to the Alter Messages tab in the List > >Settings view or would it be better to have a separate DMARC Mitigations > >tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I would find it more natural to have "Posting Policy" (which would include posting filters on size and list membership, as well as message alterations such as removing .exe files and enforcing plain text by removing or rendering HTML parts), and "Malware Mitigation", which would include IP, domain, and mailbox filters as well as DMARC. I think DMARC mitigation is probably too special to deserve its own tab. Alter messages tab works for me, but DMARC is kind of a big enough deal (as far as mail delivery goes) and sufficiently different that I agree with Mark that it's not unreasonable to give it a separate tab. I'd be willing to start it on its own and move it if we're getting too cluttered later, as long as we document it in the release notes when we do. Florian, what do you think? Probably this is way too much reorganization to do at this point, but I'd like to keep this point in mind. We are already getting reports that configuration options are hard to find just because it's different from Mailman 2. I suspect that the REST API is sufficiently flexible and regular that we'll be tempted to proliferate options, so let's try to keep them organized. We also get reports that mailman 2.1 options are hard to find -- I think I personally help someone find something at least once a month (on irc, in person, or by email) for the past decade. :) I imagine Mark has answered a lot more of those than I have. The big thing I want is good documentation here. There's never going to be an organization that works for everyone, but an easily searchable document with all the options would make a big difference. I only got to that level with the user docs not the list admin docs in 2.1 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 3.1 beta coming soon
On 2016-12-08 9:45 AM, Florian Fuchs wrote: you have a traceback somewhere? If you're logging in for the first time, it *might* have to do with allauth trying to verify your email address by sending you an confirmation email (which probably fails if you don't have smtp set up on your mac). If that's the case, we should probably try to catch this condition and display a useful error message instead of just letting it break. The email *would* make sense, and would explain why I saw the error more often associated with macs. If that's the case it sounds like an error that should be caught and explained. I'll file a bug and dump the traceback there. Terri ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] [MM3-users] Re: Mailman 3.1 beta coming soon
Barry Warsaw writes: > >I can also work on Postorius. Also in this vein I have a question. > >Should the DMARC settings be added to the Alter Messages tab in the List > >Settings view or would it be better to have a separate DMARC Mitigations > >tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I would find it more natural to have "Posting Policy" (which would include posting filters on size and list membership, as well as message alterations such as removing .exe files and enforcing plain text by removing or rendering HTML parts), and "Malware Mitigation", which would include IP, domain, and mailbox filters as well as DMARC. I think DMARC mitigation is probably too special to deserve its own tab. Probably this is way too much reorganization to do at this point, but I'd like to keep this point in mind. We are already getting reports that configuration options are hard to find just because it's different from Mailman 2. I suspect that the REST API is sufficiently flexible and regular that we'll be tempted to proliferate options, so let's try to keep them organized. Steve ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
