Hi Mark,
thanks for looking into this.
--On 8. März 2016 um 15:43:11 -0800 Mark Sapiro wrote:
I'm still having difficulty duplicating what you saw.
For the above three messages, the first one just gets detected as an
invalid date and archived under the current date by the current bin/arch.
On Mon, Mar 07, 2016 at 11:35:00AM +0100, Florian Fuchs wrote:
> There are a number of alternatives to captchas to prevent spam. None of them
> is perfect, but one I kind of like is the honeypot approach:
There are others as well. A few scattered examples:
1. Use the Spamhaus DROP and EDROP list
Hi,
As per previous discussions, it would be nice to support style
hierarchies such that the list owners can compose them and defer
settings to values higher up, that would allow the core to define some
basic styles and then list owners can just tweak a few settings to
modify one of those base styl
Hello,
I am a Computer Science Undergraduate interested in contributing to the
GSoC'16 list styles project.
I have knowledge of Python and have programmed in this language.
I am pretty much enthusiastic regarding the development of list styles for
different mailing purposes
and I seek help regard
Hi Vijay,
On 03/09/2016 01:23 AM, Vijay Dwivedi wrote:
> Hello,
>
> I am a Computer Science Undergraduate interested in contributing to the
> GSoC'16 list styles project.
> I have knowledge of Python and have programmed in this language.
Welcome!
> I am pretty much enthusiastic regarding the d
On 03/09/2016 05:26 AM, Sebastian Hagedorn wrote:
>
> --On 8. März 2016 um 15:43:11 -0800 Mark Sapiro wrote:
>
>> I'm still having difficulty duplicating what you saw.
>>
>> For the above three messages, the first one just gets detected as an
>> invalid date and archived under the current date b
>
> We played around and found that the error is related to our version of
> Python. Here's a minimal test script that shows the issue:
>
> from email.Utils import parseaddr, parsedate_tz, mktime_tz, formatdate
> print mktime_tz(parsedate_tz("Fri, 4 Feb 100 00:51:42 +0100 (MET)"));
>
> That's th
Hi,
I took the liberty of updating a couple of pages on the wiki. Noticeable
additions are the following
two pages:
http://wiki.list.org/DEV/HowToContributeGit
which is intended to be a howto regarding git. It should cover the basics by
giving example
executions of commands. Real documentation
On Mar 10, 2016, at 01:02 AM, Simon Hanna wrote:
>I took the liberty of updating a couple of pages on the wiki.
Thanks! I did a very quick pass through both pages.
Cheers,
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https:
Thanks for following up here Harshit. Here are some of my thoughts/ramblings.
On Mar 09, 2016, at 10:51 PM, Harshit Bansal wrote:
>I think the "Permissions Systems" would have nothing to do with the
>core. It would be related to Postorius. We will have to create a style
>model separately in Post
Harshit Bansal writes:
> I think the "Permissions Systems" would have nothing to do with the
> core. It would be related to Postorius. We will have to create a style
> model separately in Postorius which would store the style name and the
> user who created it. Then only the user who has creat
Barry Warsaw writes:
> It's likely that the permissions would only be enforced in
> Postorius, although we can think about how the core would enforce
> the permissions.
I don't insist on core enforcement, though I think it desirable. I do
ask that this functionality not be called "permission"
12 matches
Mail list logo
