Re: [Mailman-Users] Authenticated Received Chain in Mailman?

2017-06-06 Thread Jim Popovitch
On Tue, Jun 6, 2017 at 3:11 PM, Joseph Brennan  wrote:
> On Tue, May 30, 2017 at 10:34 PM, Brett Delmage
>  wrote:
>> Will Mailman 2 or 3 be incorporating Authenticated Received Chain (ARC) 
>> http://arc-spec.org/ ?
>
>
> Wonderful, another offering of "This document is not an Internet
> Standards Track specification; it is published for informational
> purposes" adding further complexity to email in a mad attempt to make
> up for the "potential" (?) problems that the previous "informational"
> one (DMARC) has done to mailing lists.

In the Spam fighting world these have been happening for so long they
are known as FUSSPs.

Fret not, a year or two after ARC the same people will come along with
a new spec and insist that everyone support it.  It's kind of like a
mafia, "do this or we'll shame you into doing it by promoting your
competitors on our website".

-Jim P.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Authenticated Received Chain in Mailman?

2017-06-06 Thread Joseph Brennan
On Tue, May 30, 2017 at 10:34 PM, Brett Delmage
 wrote:
> Will Mailman 2 or 3 be incorporating Authenticated Received Chain (ARC) 
> http://arc-spec.org/ ?


Wonderful, another offering of "This document is not an Internet
Standards Track specification; it is published for informational
purposes" adding further complexity to email in a mad attempt to make
up for the "potential" (?) problems that the previous "informational"
one (DMARC) has done to mailing lists.

It would be too easy for email-reading software to show me the address
of the sender and the name of the system that handed the message to my
system, and let me use my own common sense to decide whether it's
spoofed.

Well, we have to play the cards we're dealt. Onward.

Joseph Brennan
Columbia University

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Mailman-2.1.23 and reCAPTCHA

2017-06-06 Thread Mark Sapiro
On 06/06/2017 07:23 AM, SP2L wrote:
> 
> 1. The recaptcha/client directory contained from
> the beginning both __init__.py and captcha.py.
> So, "touch /usr/share/pyshared/recaptcha/__init__.py"
> wasn't necessary.


I know that the recaptcha-client package contains
recaptcha/client/__init__.py. I was suggesting that for some unknown
reason, it may also need recaptcha/__init__.py. In order for a directory
to be recognized as a Python module, it must contain a (possibly empty)
__init__.py.


> Yet another problem emerged:
> "Invalid captcha" message,
> regardless of correct response to captcha.
> 
> Need to search for solution.


I can't help with that one.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Mailman-2.1.23 and reCAPTCHA

2017-06-06 Thread SP2L

Mark.


Location  /usr/share/pyshared seem to be
specific to Debian as I just checked my old
Debian-7.11 where exactly the same exists.


Best regards.
---
Tom - SP2L

Sent from Xperia Z1 with AquaMail
http:/​/​www​.​aqua-mail​.​com



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Mailman-2.1.23 and reCAPTCHA

2017-06-06 Thread SP2L

Hello Mark.


First of all I thank you very much for such
complex and self-explanatory elucidation.

Now, I need to say  _NOT GUILTY_  in regards everything
what is beyound control of regular Linux system
user when installing OS from original DVD disc.
I mean for instance, which packages and where
being placed by installation routine.

1. The recaptcha/client directory contained from
the beginning both __init__.py and captcha.py.
So, "touch /usr/share/pyshared/recaptcha/__init__.py"
wasn't necessary.

2. The two directories:
   /usr/share/pyshared/
   /usr/local/lib/python2.7/dist-packages
were created during system install time.

3. Removed  __one additional__  space character
   before " if not...", thus solving indent issue.


Yet another problem emerged:
"Invalid captcha" message,
regardless of correct response to captcha.

Need to search for solution.


Best regards.

---
Tom - SP2L

Sent from Xperia Z1 with AquaMail
http:/​/​www​.​aqua-mail​.​com



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org