[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Aaryan Bhagat writes: > Stephen writes: > >Also, you need to think about what happens if the warning fails > >for some address. Probably you just treat that as equivalent to a > >bounce in most cases, but what happens if it's a "no such > >address"? Is that already handled? > > For the

[Mailman-Developers] GNU Mailman Season of Docs Proposal Selection

To the applicants to Google Season of Docs with GNU Mailman: Cc: Mailman Developers [This is an abbreviated version of the message sent directly to the applicants.] Thank you all for your interest in GNU Mailman, and for applying to Season of Docs with the Mailman organization. First, I would

[Mailman-Developers] Re: mailman3 merge strategies (squashing commits vs. leaving commits as they are)

Abhilash Raj writes: > + Mailman Developers, since this seems like a general discussion topic. > > On Thu, Aug 8, 2019, at 2:01 AM, Mike Gabriel wrote: > > Hi Abhilash, > > > > I just looked into the two recent merges from Daniel on mailman's > > master branch. > > > > I noticed that

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Another one that got hung up in my drafts folder. Same as the other, I think the basic coding probably is solved by now, but I'm worried we're not communicating about what the design problems are. Aaryan Bhagat writes: > According to me, I think a new command which takes all the > `Address`

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Sorry, this got hung up in my drafts folder. The basic coding probably is solved, I think, but I'm worried we're not communicating about what the design problems are. So here goes. Aaryan Bhagat writes: > Thanks for the reply, Stephen! > > Stephen writes: > >I don't understand why

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Aaryan Bhagat writes: > Stephen writes: > >My second-order response is if you still care [...], you > >can arrange to have an index on the Addresses (or a separate queue) > >which has the earliest timer first, and then process the Addresses in > >that order. > > This looks fine as of

[Mailman-Developers] Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Aaryan Bhagat writes: > - In the case of `Send_Warnings` function if the same approach was > followed, meaning it would take one by one the `Address` instances, > check tuples in the `bounce_info` attribute ( see the pr for this ) > and see whether to send a warning mail or not to can

[Mailman-Developers] GSoD 2019: Issue in submitting proposal

Update: Ananya has already come up with a reasonable solution (attach a PDF from Google doc to email), but here's my advice if anybody else runs into the same issue. Ananya Maiti writes: > Google is accepting proposal responses in a google form this time and > is asking to add the proposal

[Mailman-Developers] Re: Integration of SMS alerts for moderator approval

sandeep kumar writes: > For every mail notification that is sent to moderator for approval he > should also receive the SMS on his mobile saying so and so list is pending > for approval. > This is the requirement of the customer. For the future, you don't have to explain why you want a

[Mailman-Developers] Integration of SMS alerts for moderator approval

sandeep kumar writes: > We have requirement in mailman 3 that is when a moderator receives email > notification for a list posted he should also receive SMS alerts saying > that so and so list is pending for approval. Anything related to SMS itself is way outside of our scope. Your

[Mailman-Developers] Re: Season of docs' 19

s: > On Fri, May 31, 2019, at 12:24 AM, Stephen J. Turnbull wrote: > > Hi, > > > > I'm Steve, the org admin and principal mentor for Season of Docs > > (GSoD). The other mentor, Abhilash, is also Mailman project lead and > > org admin for Season of Code (GS

[Mailman-Developers] Season of docs' 19

Hi, I'm Steve, the org admin and principal mentor for Season of Docs (GSoD). The other mentor, Abhilash, is also Mailman project lead and org admin for Season of Code (GSoC). To pile on to those responsibilities, most of Mailman core (including all currently active devs) was at PyCon April 30

[Mailman-Developers] Hi, Season of Docs people! [was: Mailman Documentation Request...]

First let me say Hi to Ananya and Karnavee who just came in (I'm guessing names, please correct me if I'm wrong, or if you just want to go by a different name entirely). Thank you for writing! We really appreciate your interest in Google Season of Docs and in Mailman. Now, I've some more

[Mailman-Developers] We're in Season of Docs!

So, we're in Season of Docs! Currently, Abhilash and I are registered as mentor/admins. I don't think we need more admins, but more mentors is always a good thing. Hey, users! You don't need to be a programmer to mentor docs, of course, and it may be a *good* thing to *not* be a programmer and

[Mailman-Developers] Re: Interested in Working on the Mailman Documentation for GSOD

Hi, Ariessa! Thanks for your interest. Abhilash and I are attending PyCon (I'm here and VEY jet-lagged, Abhilash comes tomorrow, I think), so it'll be a couple of days before we give a detailed response. We'll be sprinting on Mailman next week (some subset of Monday-Thursday), and we'll be

[Mailman-Developers] Unique idea presentation

Hi, Kurian! (Is that how you would like to be addressed in the future?) kurian thomas (kk) writes: > Respected sir/madam, You don't need to be so formal. "Hello, I am Kurian and I'm interested in working with Mailman on GSoC" the first time, and something like "Hi folks" after that if you're

[Mailman-Developers] Questions on GSoC

kurian thomas (kk) writes: > 1)If I have a unique idea to implement do I send it to a specific email > address or add it as my proposal for GSoC? If your idea is not one of those listed on our ideas page, please send it here to mailman-developers@python.org. We may not be interested in adding

[Mailman-Developers] Re: Introduction

Rushang Gajjal writes: > I wanted the confirmation at the earliest regarding whether they > are any chances of me getting shortlisted for GSOC if I start > working now so that I can start drafting a Proposal and make a few > contributions, Pull Requests. There's no "shortlisting". You check

[Mailman-Developers] (no subject)

aaryan bhagat writes: > It is obvious that posts will not be deleted even if the user > unsubscribed. But there is a "Discussion you have commented" > section. It is linked with each user. [Addressed to all students, not a personal criticism] One should study the Mailman architecture

[Mailman-Developers] Re: Loss of data when unsubscribed?

Aaryan Bhagat writes: > Well in a crux when the user will resubscribe he will see its > previous posts. We have an implementation for that already right? I read Mark's reply, but I'm still not understanding what you are thinking about. It doesn't seem to be the archive (which after all may

[Mailman-Developers] Loss of data when unsubscribed?

Aaryan Bhagat writes: > When we unsubscribed a user after sending a probe. We currently > remove it from the list's roster. Let's suppose the email is > resubscribed. Will the discussion the email has posted earlier will > remain there or the account will start fresh as any other new >

[Mailman-Developers] HOWTO: GSoC proposals (for Mailman)

To our GSoC applicants: You may want to read https://turnbull.sk.tsukuba.ac.jp/Blog/SPAM.txt before you submit (or edit before we read it ;-), for a better first impression. It's not a "spec" you should "try" to conform to in your first draft -- many of the activities discussed are precisely

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

Aaryan Bhagat writes: > >The other kind are DSNs of some type returned to a LIST-bounces > >address. These are processed by flufl.bounce > > which determines whether > >the failure is temporary or permanent and reports that to the > >bounce runner. >

[Mailman-Developers] Re: GSoC deadlines approaching fast!

) task. I'll try to get at GSoC stuff in the afternoon. Steve Abhilash Raj writes: > > > On Sun, Feb 3, 2019, at 9:25 PM, Abhilash Raj wrote: > > On February 1, 2019 2:32:34 AM GMT+05:30, Terri Oda > > wrote: > > > > > > > > >On January

[Mailman-Developers] GSoC deadlines approaching fast!

Hey all We need to decide if we're going to go under the PSF umbrella or if we want to go standalone. The real advantages to the standalone are two tickets (most expenses paid by Google) to the Mentor Summit, and the $500/student gift to Mailman. But it's more work and lower chance of

[Mailman-Developers] [MM3-users] Re: digests are created but not sent out

This subthread moved from Mailman3 Users list. ASIDE: This got caught for several days in a mismatch between Exim and greylisting. If you're an Exim user, recent versions are pretty aggressive about using the PIPELINING and CHUNKING extensions to SMTP, and one or both of those seems to be a

[Mailman-Developers] New gitlab subproject for UX?

Máirín Duffy writes: > If that sounds reasonable and you'd have me, can you help set me up > with a UX subproject? My gitlab username is mairin. I don't have a lot of time, and subprojects are Abhilash's business, but I'd like to help. I agree with you and others that it's important. Like

[Mailman-Developers] Re: GDPR disclaimers and redaction in mailman 2

John Levine writes: > In article <20180726083240.horde.yz7mtoof32nssryse90t...@andreasschulze.de> > you write: > > > >John Levine: > > > >> Another is to provide different views of what lists exist depending on > >> what IP address you're connecting from, so internal lists are only > >>

[Mailman-Developers] Firefox loves us! Leftmost "top site"!

>From the Silly but Encouraging Fact of the Day Department http://turnbull.sk.tsukuba.ac.jp/MailmanFTW.png Note the empty "Highlights" box: I haven't used Firefox in a long time, just checking that another browser isn't broken on one of my employer's sites. So this *isn't* because I visit

Re: [Mailman-Developers] Small contrib script - Autoconf

Lindsay Haisley writes: > > The bottom line is this is something that newer autoconf does and > > if your autoconf does it, I don't know a way to turn it off. > > I looked at the code and that's kinda what I figured. Thanks The autotools authors are *extremely* prescriptive, and try to

Re: [Mailman-Developers] Handling additions to REST API in client side

Simon Hanna writes: > Up until now I was under the impression that the clients > (Postorius/Hyperkitty) always require the latest version of core. We don't require that the client be Postorius or Hyperkitty though. While in one sense we're not responsible for what third party clients do *at

[Mailman-Developers] Handling additions to REST API in client side

Abhilash Raj writes: > There is no easy way to check for whether the Core has this > attribute as API is versioned at 3.1 for both cases. Barry has spoken (later, in a parallel thread) to the effect that this isn't a real problem "most" of the time. But to me it seems like the obvious ways

Re: [Mailman-Developers] Use of the public suffix list

Alessandro Vesely writes: > Yes, RDAP is WHOIS with a machine-readable format. In both cases, > a name retrieved from a public domain name registry (DNR) is an > "organizational" domain. Yes, but my understanding of the discussions on the DMARC list leading to use of the PSL in RFC 7843 is

[Mailman-Developers] Use of the public suffix list

Alessandro Vesely writes: > * The specs say that "DMARC should be amended to use [a method > better than PSL] as soon as it is generally available" [1]. I > believe that sentence refers to RDAP, which was released more or > less at the same time (March 2015) [2]. > > [1]

Re: [Mailman-Developers] Signing commits with gpg

Mark Sapiro writes: > where linus argues that "Signing each commit is totally stupid." and > that you should sign tags but not commits. I agree with Linus that signing all commits is probably unnecessary because of the SHA1 chain, but I disagree with signing only tags. I think that the

Re: [Mailman-Developers] Extracting some Mailman code

Alessandro Vesely writes: > I'm unclear how adding a Reply-To:, depending on users' clients is > going to affect mailing list traffic. For an alternative, when the > usual action is to reply to mailing list, it seems to me to be > smoother to just mangle the From: so as to make it like so:

Re: [Mailman-Developers] Extracting some Mailman code

I gather you have completed your program already, but I had this in the works and it might be useful for people doing similar things. Lindsay Haisley writes: > Is there any reason to pull in a more recent MM 2 and use the DMARC > detection code therein? Speed is important here since this is

Re: [Mailman-Developers] Migrating Postorius and Hyperkitty to Python 3

Terri Oda writes: > What's the state for Centos? I think it was the last likely distro > we cared about with old python needs, but I'm not sure core > supports it at all any more. Do we need to worry about current distros? We're still seeing plenty of questions about new installations of

Re: [Mailman-Developers] GDPR

noskcaJ leahciM writes: > It's the law. Some of us have to deal with it; like it or not. > GDPR merely calls for explicit consent (where appropriate). E.g. > A picture is worth a thousand words: None of this is helpful to me; as far as I can tell it's not responsive to what I wrote or

Re: [Mailman-Developers] GDPR

noskcaJ leahciM writes: > | tl;dr > > Too long: The regulation and articles are even longer. > > Didn't Read: But you replied none-the-less ;-) I read EVERYTHING. Above is advice to my readers: "I read, so you don't have to". ;-) I feel sorry for anyone who hangs out in places where

[Mailman-Developers] GDPR

tl;dr I don't think this is worth thinking about until we get a request from users who actually are threatened with liability for their Mailman installations. Suggestions from where we can obtain funding to do this stuff? The harder parts are non-trivial. noskcaJ leahciM writes: > 1. The term

Re: [Mailman-Developers] Discourse Integration

Vaibhav Lohani writes: > Stephen J. Turnbull <turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > What sort of integration do you have in mind? > > The idea is to have a two way binding sort of integration, where the > conversations can be carried out in discourse

Re: [Mailman-Developers] [GSoC] Encrypted mailing lists

Hi Jan! Congratulations on being selected! Note that Mailman is a PSF suborg, so you have to comply with PSF reporting standards. I'll get back to you if you need to do anything more. The only thing I can think of offhand is to register with the PSF "planet" (or whatever they're using to

[Mailman-Developers] Add information on first line of email

David Terni writes: > Hi, > I need to use the text of "description or information filed" used to > describe the mailinglist and put this information in the firsts lines > e-mail. Like the credits but on head of email. > > How I can do it? You'll have to manually copy it to the "Header"

Re: [Mailman-Developers] Signaling One-Click Functionality for List Email Headers

John Levine writes: > Patrick wrote: > >Is that something mailman(2|3) should support? To me it looks > >useful. Personally I am +1 on "patches welcome" until users start asking for it (including via list and site managers). Until I see evidence of intent to use, I'm not excited about

Re: [Mailman-Developers] Encrypted lists predictable difficulties and implementation needs

After I wrote most of this, I see Norbert covered some of the same points, but from the point of view of his specific use case. So I'm just going to send despite a bit of redundancy. Rich Kulawiec writes: > Granted, this will diminish as more communications become encrypted, but > for the

Re: [Mailman-Developers] How to set up mailman 3

Barry Warsaw writes: > up on the state of the art, but IIRC, there were Python libraries that could > generate bindings based on WADL. That sounds cool, but I tend to feel that WADL gets pretty heavy. If we can't just mark things with something like "@exported_REST", it's not clear that the

Re: [Mailman-Developers] How to set up mailman 3

Barry Warsaw writes: > On Mar 29, 2017, at 02:07 PM, Stephen J. Turnbull wrote: > > >Would it be possible to automate this? I haven't thought carefully > >about it, specifically security issues. However, there could (in > >theory) be an automated export of "al

[Mailman-Developers] How to set up mailman 3

On [MM3-users] Mark Sapiro writes: > On 03/25/2017 04:55 PM, Mark Sapiro wrote: > > > > A list's message_size can't currently be set in Postorius. File an issue > > at . > > Actually the attribute name is max_message_size, not message_size.

Re: [Mailman-Developers] Encrypted lists predictable difficulties and implementation needs

Jan Jancar writes: >b) Added complexity, maintenance cost to Mailman's infrastructure. > This can be mitigated by implementing encrypted mailing lists > either as a plugin as was proposed here before, In one sense, a plugin is the ONLY way this feature can be reasonably implemented

[Mailman-Developers] GSoC Help Wanted

Muhammad Rizvi writes: > I want to let you that I want to take part in Python Organization but don’t > exactly know what to do. The thing that I came to know so far is that, > first I have to find a mentor but don’t know from where I can contact a > mentor, secondly I have to submit a

[Mailman-Developers] Encrypted lists are still a valid GSoC project, in case you were wondering.

Terri Oda writes: > Basically, don't just read "Why Johnny Can't Encrypt" [1] and assume the > problem of encrypted is dead and never will be solved. But you might want also to read JWZ's blog on Signal[2] *and all the comments* to see why threat models matter, and how subtle it can be. (If

Re: [Mailman-Developers] Encrypted lists predictable difficulties and implementation needs

Rich Kulawiec writes: > (In the specific case, e.g., the right people using the right > devices with the right knowledge and self-discipline: maybe. But > there are not many of those cases and any of them can revert to the > general case in seconds with one poor decision or perhaps even >

Re: [Mailman-Developers] Encrypted lists predictable difficulties and implementation needs

Richard Damon writes: > One big thing that I haven't seen in the discussion of this problem is > exactly WHAT issue/problem this feature is intended to solve, There are > several different problems that encryption can help with, each needing > different sort of support from the software.

Re: [Mailman-Developers] Encrypted lists predictable difficulties and implementation needs

I hope it doesn't surprise anybody that despite being proponent of this project I'm quite sympathetic to Rich. Barry Warsaw writes: > That assumes an open membership policy. Wouldn't much of this be > mitigated with a closed subscription policy? Not if the target membership isn't already

Re: [Mailman-Developers] Encrypted lists predictable difficulties and implementation needs

Rich Kulawiec writes: > What all of this means is that once a list passes N members, where > we can debate about N, the probability that at least one of those > members has already been compromised even before they've joined the > list starts rapidly increasing. This is true, but you've

[Mailman-Developers] Project idea understanding

raditya writes: > 1) Each message will be encrypted with all users as recipients. You are way ahead of yourself. Before thinking about *how* to manage an encrypted list, both operationally and socially, we need to decide (1) *who* is going to be posting (2) *why* are they posting to an

[Mailman-Developers] Gsoc idea explanation needed

Posted to this list yesterday. Probably crossed in the mail. Check the archives. > Dear mentors, could you give me a rough idea about the level of > knowledge required in crypto libraries of python, and also possible > sources of learning. ___

[Mailman-Developers] Mailman 3 Project discussion

Manpreet Singh via Mailman-Developers writes: > My question is apart from this, on what areas of coding, team will > be working on specifically which python library, framework etc for > this project ? And do you want us to learn specifically new > technology apart from python to successfully

Re: [Mailman-Developers] In regard to GSoc-17

Barry Warsaw writes: > Note that 3.4 is also an officially supported version for core. Yes. Let me clarify that I was referring to what the mentor (me ;-) is willing to support for this GSoC project (in the interest of minimizing the motion of the target platform for the intern; that's also

[Mailman-Developers] Discourse Integration

Vaibhav Lohani writes: > There was a mention of integrating mailman 3 with discourse some > times back. I am interested in working on it. Is someone else > interested in it or already working on it ? I don't know of anyone who is currently working on it, nor do we have specific plans at the

[Mailman-Developers] In regard to GSoc-17

Hi, Apart from what Abhilash wrote, I have a few ;-) additional comments. Bhavishya writes: > Hi, I saw the idea to create various kinds of encrypted lists, > Could you elaborate the following: > 1)The amount of knowledge of security (and if possible the sources > to achieve the same) You

Re: [Mailman-Developers] What characters should be allowed in listnames

Mark Sapiro writes: > That doesn't really address my question. That has to do with > internationalized email addresses. Granted the listname must be a valid > local part of an email address, but that doesn't mean every valid local > part has to be a valid list name. The problem that I

[Mailman-Developers] What characters should be allowed in listnames

Mark Sapiro writes: > I'd like feedback on this. What are your thoughts on what characters > should be allowed in list names? Uh, RFC 6532 Probably that can wait for when we actually support it :-), but while you're doing this we should (= I should when life gets sane ;-) make sure that

[Mailman-Developers] Development Enviromnent setup

Diptanshu Jamgade writes: > I did `mailman info -v`. This returned me with this (error)[ > http://pastebin.com/wLzDQwAu], Kindly help. In the future, when you don't have any idea what your problem is, please report as a bug at GitLab (right now GitLab is down I hear?), or attach the trace to

Re: [Mailman-Developers] Development Enviromnent setup

Barry Warsaw writes: > All that said, if you can't import _sqlite3, then your Python > installation is messed up. That's a stdlib module so it should > always be around. But distros! Probably @ncoghlan_dev's fault. ;-) ___ Mailman-Developers

[Mailman-Developers] Reg: Postorius Issue 127

Siddhartha Gairola writes: > So this is what we have to implement for postorius - > "if the post is from a moderated member, the moderator has a checkbox to > clear the member's moderation when accepting the post." Right. > But I am not too sure how to get this done. I guess it would

Re: [Mailman-Developers] Reg: core and Hyperkitty issues

Barry Warsaw writes: > Cool! Have you looked through the Gitlab issues for both trackers? > Are there any that interest you? He and I are already working on Postorius #127. Kibitzers welcome! Steve ___ Mailman-Developers mailing list

[Mailman-Developers] Reg: Postorius Issue 127

Siddhartha Gairola writes: > I would like to work on Postorius issue 127 - > https://gitlab.com/mailman/postorius/issues/127. > > I would be grateful if someone could tell me how to start solving this. You start by starting. ;-) "Claiming" the issue and posting here was a good start. :-)

[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

Re: [Mailman-Developers] PGP support for MM3

Mark Sapiro writes: > On 11/18/2016 07:26 AM, Dominik wrote: > > I'd like to see PGP support for MM3 but I thought it might be a little > > to early to file an issue. It's too late. :-) The issue has already been raised, years ago. So far the complexity has deterred people from actually

Re: [Mailman-Developers] Docker files for mailman

Danil Smirnov writes: > Okay I've found that image can be built if you base on Ubuntu Trusty distro > (line 6 of the Dockerfile: "FROM ubuntu:trusty") and add ruby-sass to the > set of packages to install (line 13: "apt-get install -y git python3-dev > python3-pip python-dev python-pip

[Mailman-Developers] Mailman Sprint was fun at PyCon 2016 Canada!

Note updated Subject. ;-) First time as a sprint leader, got really lucky with the sprinters. ellmetha did a bunch of work (4 MRs!) without a word [of English ;-]; I talked with mdupuis quite a bit but didn't need to look at any of his code at the time. I don't know if the code is up to snuff,

Re: [Mailman-Developers] Mailman Sprint happening NOW at PyCon 2016 Canada

Mark Sapiro writes: > On 11/14/2016 03:52 PM, Barry Warsaw wrote: > > I'm not sure how useful bundler is either. It was a good idea at the time, but IMO it will be way too much work to keep up to date as is. If we must provide a bundle, I think we should use something like Simon's script

[Mailman-Developers] Adding gitlab group members and permissions

I added a new group member (mdupuis) with Reporter permission, and upgraded existing members (adammendoza, aniketshukla, khushbuparakh) to "Reporter". Dunno what policy is but Reporter looks pretty harmless, and Guest is pretty crippled (can't even set tags). WDOT? Steve

[Mailman-Developers] Adding gitlab group members and permissions

I added a new group member (mdupuis) with Reporter permission, and upgraded existing members (adammendoza, aniketshukla, khushbuparakh) to "Reporter". Dunno what policy is but Reporter looks pretty harmless, and Guest is pretty crippled (can't even set tags). WDOT? Steve

[Mailman-Developers] Mailman Sprint happening NOW at PyCon 2016 Canada

Just to let you know. Also, I've done a little tracker curation (specifically HyperKitty), mostly tagging -- probably you should assume nothing important is happening if you get notices. Steve ___ Mailman-Developers mailing list

Re: [Mailman-Developers] MM3 DMARC mitigations

Barry Warsaw writes: > It will probably make no difference, but if we can inform users as > to the real culprits in this mess, they can either complain to > their ISPs or vote with their feet and find a new provider. That > won't happen if they continue to blame the list software or site.

Re: [Mailman-Developers] Camera-ready option to mitigate DMARC issues

Alessandro Vesely writes: > Camera-ready is cleaner than anything I have heard till now. Clean, maybe, but Mark explained why the scheme is fragile even if you can get participation. The killer problem is personalization, but the other problems are also intractable. Serial numbers in the

Re: [Mailman-Developers] MM3 DMARC mitigations

Removing known MM-DEV subscribers, the CC list is getting long. David Andrews writes: > At 11:06 AM 11/5/2016, Mark Sapiro wrote: > > >However, I've just become aware that Microsoft has implemented another > >"feature". [...] one of the tests is the To: and > >From: addresses are the same.

[Mailman-Developers] Camera-ready option to mitigate DMARC issues

Alessandro Vesely writes: > The idea is to add a footer only in case it is not present, Aside from the technical difficulties that Mark describes, this suffers from a really big defect: for this to be actually useful, you'd need near-100% participation (Authenticated Received Chain has the same

[Mailman-Developers] GNU Mailman Architectural Patterns & Quality Attributes for Research

Hi Michael, Did you ever get an answer to this request? I broke a bunch of ribs on the 14th and have been pretty useless for the last two weeks, but now I have a chance to catch up on correspondence of less than "life or death" importance. Regards Steve Michael Skeen writes: > Hello GNU

Re: [Mailman-Developers] Setting up installation to test own changes

Mark Sapiro writes: > Mailman bundler is not recommended because it doesn't install the > current development branches. Mailman 3.1 is "close" to release (how close is for Barry, Florian and Aurelian to say, but the improvements over 3.0 in the dev branches are substantial). I strongly (as

Re: [Mailman-Developers] Request to process merge requests faster

Terri Oda writes: > I can't speak for anyone else, but I had some big life events this > summer, So have others, though I won't speak for them either. > > I know all core devs are volunteers, and no one is maintaing the > > Mailman projects full-time, but it's a little frustrating to have

Re: [Mailman-Developers] Remediation for fake member creation

Franck Martin writes: > May be a captcha? Or some more modern techniques... Captchas aren't applicable to email requests. It will be harder than that. We could turn off subscription by email after user creation so that users would get only one email per email at most. From Mailman's point of

[Mailman-Developers] DMARC and Mailman 3

Twilley, Jack writes: > I have been sponsored by an organization to port the existing DMARC > code from Mailman 2.1 to Mailman 3. While my primary > responsibility is to satisfy the organization's requirements, it is > very important to me that the resulting product be a viable > candidate

[Mailman-Developers] Thinking about Gmane

Barry Warsaw writes: > Lars seems to say that it's more likely that the NNTP/SMTP bridge > will survive, but not the web ui. I would expect this, since NNTP and SMTP both have independent clients. But the Web UI *is* the client (not the browsers, which are "thin" clients). That means that

Re: [Mailman-Developers] GSoC project - Implement module to process ARC headers

Aditya Divekar writes: > So should a new conversation be started with Mark for > our request? I/we need to find out exactly what we need. We may want to do this through email-test.python.org (no-existent, for example, python.org is the relevant part, or maybe a private domain of someone's),

Re: [Mailman-Developers] GSoC project - Implement module to process ARC headers

Aditya Divekar writes: > So if we have a domain name associated with the ip, I'll go ahead > and make the TXT records. Else, we'll have to create a new one. > I'm not aware of any way to avoid this. Let me know if you are > aware of any :) Ah, that's a problem. I don't have control of the

[Mailman-Developers] GSoC project - Implement module to process ARC headers

Hi! I'm sorry that I haven't responded before, it's been very busy catching up to $DAYJOB since getting back. > Now the next step would be to change the namespace and make it more > general to accommodate the ARC capability. That is the module now > provides the capability for ARC protocol

[Mailman-Developers] Postorius: Search Plugin for List

Khushbu Parakh writes: > I am working on search plugin for lists You're proposing to find information about lists, not posts, right? What search criteria do you propose? Just name ~= posting address ~= List-Id? > and wondering what would be the best approach, using Ajax Think about why you

Re: [Mailman-Developers] [Email-SIG] Some parsing/generation issues of email in Python 3

Hans-Peter Jansen writes: > > I'm willing to bet it will converge to "robust in practice" much > > faster than the previous design did. > > I will take your word on that. Why take my word when you can take my money instead? :-) Keep on with the porting project! > > Patience and

Re: [Mailman-Developers] New Interface

Harshit Bansal writes: > How can this composability be achieved in a model? I mean that the > size of a table is fixed in a model and if a style describes just a > partial set of attributes then what would be stored in other > attributes? (1) In a NoSQL database (MongoDB, for example), you

Re: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3

Simon Hanna writes: > I used Zanata, but found it not very intuitive to use. It's also > painfully slow. Thanks for your efforts here, it's very helpful. > So If you give me the ok, I write the gnu pootle maintainers and ask > them to create three projects for us. +1 from me. Pootle is

Re: [Mailman-Developers] Authorization System in Core

Simon Hanna writes: > While in theory it would be possible to enforce permissions in core > about who is allowed to call specific rest calls, this would > require a lot of changes. I'm not sure we want to go this way. Mailman is used in a lot of enterprises contexts, where the system

[Mailman-Developers] FWD: [dmarc-ietf] Last Call: (Interoperability Issues Between DMARC and Indirect Email Flows) to Informational RFC

Hi, all This IETF work affects us all, so I'm reposting here so those with the interest can participate. "Indirect mail flows" includes but is not limited to mailing lists. "DMARC" is the protocol which Yahoo! and AOL used to unsubscribe thousands of innocent list members in April 2014. This

Re: [Mailman-Developers] Regarding System set up

By the way, Aditi is my student under the Systers org. Please take good care of her! Thanks to Simon and Aditya for getting started already! :-) Aditya Divekar writes: > It seems you ran into the error due to the incompatible falcon version. > You should have falcon==0.3 installed for the

Re: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3

-i18n removed, I'm not subscribed. Barry Warsaw writes: > We need a Mailman 3 translation champion, someone who understand > the technical and more importantly, social issues involved, and can > spend time and energy on helping bring a good story to fruition. > I'm happy to give wide

Re: [Mailman-Developers] mailman

treal tv writes: > The problem is that when python 3.4 makes a virtualenv, it somehow pulls > in falcon1.0.0rc1... even if you have falcon0.3.0 installed. Barry has that pinned to < 1.0 in 3.0.3, do a diff against 3.0.2 (or maybe just grep the logs) and you should find out how to stop that.

Re: [Mailman-Developers] Interest in "Implement module to process ARC headers" project GSoc

nitish salwan writes: > I know that was late but I wanted to take part in GSOC. And now > when the submission deadline is over,can I contribute in this > project through GSOC or separate contribution. You can certainly contribute at any time. About GSoC, if you submitted a proposal, I'm not

<    1   2   3   4   5   6   7   8   9   10   >