Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

John Levine writes: > I wouldn't waste time worrying about whether various hacks might make > it 0.0001% easier to phish people. Will you please stop focusing on *your* logic, and start thinking about what happens if people with different interpretations of the facts take action on those interp

Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

SM writes: > >RFCs must be shown to work in practice before they become Proposed > >Standards. Ie, don't expect something to work until you see it. > > This is a nit. There isn't any requirement that RFCs have to be > shown to work in practice before they become Proposed Standards. Don'

Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

John R Levine writes: > > > One advantage of this hack is that you can just turn it off when > > > you don't need it, much easier than the stuff that puts the list > > > address in the From: line which affects everyone. > > > > You're wrong on both counts. In Mailman 2.1.18, "From" munging i

Re: [Mailman-Developers] Mailman 2.1.18 final release

On 05/03/2014 11:30 AM, Mark Sapiro wrote: > I'm pleased to announce the final release for Mailman 2.1.18. It appears that the from_is_list and dmarc_moderation_actions Wrap Message actions may run afoul of this issue in the Python email library in versions olde

[Mailman-Developers] mailman-bundler-3.0b2: WSGI server error with zope.interface

Tim Marx writes: > "/var/tmp/mailman/mailman-bundler/eggs/zope.component-4.2.1-py2.7.egg/zope/component/__init__.py", > > line 19, in > from zope.interface import named > ImportError: cannot import name named > --

[Mailman-Developers] mailman-bundler-3.0b2: WSGI server error with zope.interface

Hello, I wanted to test the new mailman-bundler-3.0b2 and ran into a problem I could not solve. I'm not sure if it's a problem with the mailman-bundler or with my machine. So I'm sorry for bothering you if the problem might be only on my server. I installed the latest revision (#13) of the b

Re: [Mailman-Developers] [Bug 1130957] Re: Unicode errors in mailman3

Am 30.04.2014 23:53, schrieb Barry Warsaw: On Apr 30, 2014, at 09:38 PM, Tim Marx wrote: I'm using mailman 3.0.0b4 (with mailman-bundler) and ran into the same problem as described above. Luckily I found this bug report and could manage to fix it with the patches above. May I ask anybody (wit

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project

Hi, I have elaborated the implementation and the motivations behind the current approach in the following blog post, in case it might help reviewing the code better. http://myfossblog.blogspot.in/2014/05/lets-talk-over-cup-of-code.html ___ Mailman

Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

> One advantage of this hack is that you can just turn it off when > you don't need it, much easier than the stuff that puts the list > address in the From: line which affects everyone. You're wrong on both counts. In Mailman 2.1.18, "From" munging is equally easy to turn off -- two clicks on an

Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

Hi Stephen, At 01:07 05-05-2014, Stephen J. Turnbull wrote: Nor do I. I point to the *possibility* and our lack of ability to predict effects. The RFCs have proven over time to give us a system that works smoothly. We have rules of thumb that help to understand why they work as well as they do

[Mailman-Developers] Handling non-standard or obfuscated DSNs for DMARC rejects

It just occurred to me that (at the expense of a DNS query) many sites can distinguish DMARC rejects pretty well by doing a DNS query for the >From address (which I think we should be able to get, at least most of the time). This may not help much if you have most of your users posting from p=reje

Re: [Mailman-Developers] Mailman-Suite demo server

> Currently there is no links to migrate between postorius(the mailman3 web > ui) and hyperkitty(the archiver). Yeah, and that's something I'll fix as soon as I'm done squashing the main bugs I have in my pile. Aurélien ___ Mailman-Developers mailing li

Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

Mark Rousell writes: > I do not think that this method of working around Yahoo's DMARC > implementation will necessarily Nor do I. I point to the *possibility* and our lack of ability to predict effects. The RFCs have proven over time to give us a system that works smoothly. We have rules of

Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge

John R Levine writes: > One advantage of this hack is that you can just turn it off when > you don't need it, much easier than the stuff that puts the list > address in the From: line which affects everyone. You're wrong on both counts. In Mailman 2.1.18, "From" munging is equally easy to tur