Re: [Mailman-Developers] Rosters not using 'ISubscriptionService' Interface.

2016-03-31 Thread Barry Warsaw
On Apr 01, 2016, at 01:59 AM, Harshit Bansal wrote:

>I was looking at the 'rosters.py' and I am unable to understand that
>why are rosters not using 'ISubscriptionService' interface instead of
>making raw queries for finding members? Is there any reason for doing
>so and if no then should it be changed?

The easy answer is that rosters (and the IRoster interface) predates
ISubscriptionService by quite a bit.  The latter was added primarily to
support REST APIs for member searchers.

The concept of a roster as a query is pretty fundamental, and the idea was
also that rosters should be composable.  I'm not keen on changing these
interfaces.

Cheers,
-Barry

___
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] Rosters not using 'ISubscriptionService' Interface.

2016-03-31 Thread Harshit Bansal
Hi,
I was looking at the 'rosters.py' and I am unable to understand that
why are rosters not using 'ISubscriptionService' interface instead of
making raw queries for finding members? Is there any reason for doing
so and if no then should it be changed?

Thanks,
Harshit Bansal.
___
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] Correcting the display name in the recipient address

2016-03-31 Thread Barry Warsaw
On Mar 25, 2016, at 05:58 PM, Aditya Divekar wrote:

>> A perhaps more convincing example would be an extension to anonymous
>> lists with personal reply-to.  This could be accomplished by creating
>> a mailbox at the list host, which would be associated with the user so
>> she can set options for it (eg, which address to forward to), but
>> should not have a display name associated with it, and certainly not
>> the user-level display name (which in organizational contexts --
>> including Python! -- is likely to be a real name).
>>  
>Actually, the code has already been merged for the above mentioned
>automatic fallback on the user display name. So I'm not really sure about
>the next step in this issue, and think that Barry would be better qualified
>to give an opinion here than me.

Two things to keep in mind.  This comes into play for messages that Mailman
crafts out of whole cloth for notifying the user of something.  It won't be
used in messages posted to the list.

Also, although currently there's no distinction, there *could* be a difference
between None and the empty string for display_name.  The former could mean
no-fallback.

Cheers,
-Barry


pgp3G6FoF7LNE.pgp
Description: OpenPGP digital signature
___
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

2016-03-31 Thread treal tv
I've been checking all the logs for hints, but I have a feeling I missed 
a big hint in there now. I'll try 3.0.2, thanks


On 03/31/2016 10:30 AM, Stephen J. Turnbull wrote:

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.



___
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

2016-03-31 Thread Barry Warsaw
On Mar 31, 2016, at 07:36 AM, Mark Sapiro wrote:

>We are not yet compatible with falcon 1.0, see
>.
>
>You need to find where in your installation falcon 0.3 is installed and
>replace the falcon 1.0 things in venv-3.4/lib/python3.4/site-packages
>with symlinks to the corresponding falcon 0.3 directories.

I think, but haven't tried, that if you blow away the falcon 1.0 directories
in your venv, then install mailman-3.0.3 you should get falcon 0.3.  Double
check Mailman's setup.py, which should now pin Falcon to < 1.0.

Cheers,
-Barry


pgpxZcWt5KAKH.pgp
Description: OpenPGP digital signature
___
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

2016-03-31 Thread treal tv
I should also mention that I've done a full sweep of my system to make 
sure falcon 1.0.0rc1 isn't hiding anywhere. I can only suspect it's 
built into some other package and I need to hunt it down.


On 03/31/2016 10:18 AM, treal tv wrote:
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.


I've spent the last couple days fighting with this exact problem and 
trying to find ways to trick python 3.4 to not pull in falcon 1.0 when 
making a virtualenv, no solution yet though. I suspect I'm going to 
have to rebuild python 3.4.4 a few times before getting it.


On 03/31/2016 10:09 AM, Christian Schoepplein wrote:

Hi Aditya,

On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote:

   I'm sorry for the misdirect. I'm myself a beginner here!

Absolutely no problem, every hint is welcome :-).

I'm also a beginner with mailman 3 and absolutely no python expert
:-(. To be honest it is not easy to understand the full procedure of
installation of all needed components for mm3, at least if you like to
install not the mailman_bundler package. There are so many sites with
documentation and it is not easy to find out what is the right one. A
step to step guide to install all components, which also beginners or
not python programmers do understand,  would be great. Maybe there is
some kind of such a guide, but I haven't found it. And if it is not, I'd
like to help to create such a guide, but I'd need support from people
with mor knowledge of python and all the things which are needed.


   This issue on gitlab is probably the same as the one you are facing.
   The fix recommended is the installation of falcon 0.3.0.1 or 0.3
[1]https://gitlab.com/mailman/postorius/issues/122#note_4509503

If I understand it correctly, I already have a newer version of falcon
installed:

root@mm3:/opt/mailman-bundler# find . -name *falcon*
./venv-3.4/lib/python3.4/site-packages/falcon
./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info
./venv-3.4/bin/falcon-bench
root@mm3:/opt/mailman-bundler#

But as said before, I'mno python expert...

Ciao and thanks again for your help,

   Schoepp



___
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/trealtv%40yandex.com


Security Policy: http://wiki.list.org/x/QIA9


___
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/trealtv%40yandex.com


Security Policy: http://wiki.list.org/x/QIA9


___
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

2016-03-31 Thread treal tv
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.


I've spent the last couple days fighting with this exact problem and 
trying to find ways to trick python 3.4 to not pull in falcon 1.0 when 
making a virtualenv, no solution yet though. I suspect I'm going to have 
to rebuild python 3.4.4 a few times before getting it.


On 03/31/2016 10:09 AM, Christian Schoepplein wrote:

Hi Aditya,

On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote:

   I'm sorry for the misdirect. I'm myself a beginner here!

Absolutely no problem, every hint is welcome :-).

I'm also a beginner with mailman 3 and absolutely no python expert
:-(. To be honest it is not easy to understand the full procedure of
installation of all needed components for mm3, at least if you like to
install not the mailman_bundler package. There are so many sites with
documentation and it is not easy to find out what is the right one. A
step to step guide to install all components, which also beginners or
not python programmers do understand,  would be great. Maybe there is
some kind of such a guide, but I haven't found it. And if it is not, I'd
like to help to create such a guide, but I'd need support from people
with mor knowledge of python and all the things which are needed.


   This issue on gitlab is probably the same as the one you are facing.
   The fix recommended is the installation of falcon 0.3.0.1 or 0.3
   [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503

If I understand it correctly, I already have a newer version of falcon
installed:

root@mm3:/opt/mailman-bundler# find . -name *falcon*
./venv-3.4/lib/python3.4/site-packages/falcon
./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info
./venv-3.4/bin/falcon-bench
root@mm3:/opt/mailman-bundler#

But as said before, I'mno python expert...

Ciao and thanks again for your help,

   Schoepp



___
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/trealtv%40yandex.com

Security Policy: http://wiki.list.org/x/QIA9


___
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

2016-03-31 Thread Stephen J. Turnbull
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.

___
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

2016-03-31 Thread Mark Sapiro
On 3/31/16 7:09 AM, Christian Schoepplein wrote:
> 
> I'm also a beginner with mailman 3 and absolutely no python expert 
> :-(. To be honest it is not easy to understand the full procedure of 
> installation of all needed components for mm3, at least if you like to 
> install not the mailman_bundler package. There are so many sites with 
> documentation and it is not easy to find out what is the right one. A 
> step to step guide to install all components, which also beginners or 
> not python programmers do understand,  would be great. Maybe there is 
> some kind of such a guide, but I haven't found it. And if it is not, I'd 
> like to help to create such a guide, but I'd need support from people 
> with mor knowledge of python and all the things which are needed.


I feel your pain.


>>   This issue on gitlab is probably the same as the one you are facing.
>>   The fix recommended is the installation of falcon 0.3.0.1 or 0.3
>>   [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503
> 
> If I understand it correctly, I already have a newer version of falcon 
> installed:
> 
> root@mm3:/opt/mailman-bundler# find . -name *falcon*
> ./venv-3.4/lib/python3.4/site-packages/falcon
> ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info
> ./venv-3.4/bin/falcon-bench
> root@mm3:/opt/mailman-bundler#


We are not yet compatible with falcon 1.0, see
.

You need to find where in your installation falcon 0.3 is installed and
replace the falcon 1.0 things in venv-3.4/lib/python3.4/site-packages
with symlinks to the corresponding falcon 0.3 directories.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
___
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

2016-03-31 Thread Christian Schoepplein
Hi Aditya,

On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote:
>   I'm sorry for the misdirect. I'm myself a beginner here!

Absolutely no problem, every hint is welcome :-).

I'm also a beginner with mailman 3 and absolutely no python expert 
:-(. To be honest it is not easy to understand the full procedure of 
installation of all needed components for mm3, at least if you like to 
install not the mailman_bundler package. There are so many sites with 
documentation and it is not easy to find out what is the right one. A 
step to step guide to install all components, which also beginners or 
not python programmers do understand,  would be great. Maybe there is 
some kind of such a guide, but I haven't found it. And if it is not, I'd 
like to help to create such a guide, but I'd need support from people 
with mor knowledge of python and all the things which are needed.

>   This issue on gitlab is probably the same as the one you are facing.
>   The fix recommended is the installation of falcon 0.3.0.1 or 0.3
>   [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503

If I understand it correctly, I already have a newer version of falcon 
installed:

root@mm3:/opt/mailman-bundler# find . -name *falcon*
./venv-3.4/lib/python3.4/site-packages/falcon
./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info
./venv-3.4/bin/falcon-bench
root@mm3:/opt/mailman-bundler#

But as said before, I'mno python expert...

Ciao and thanks again for your help,

  Schoepp



signature.asc
Description: Digital signature
___
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

2016-03-31 Thread Aditya Divekar
I'm sorry for the misdirect. I'm myself a beginner here!

This issue on gitlab is probably the same as the one you are facing. The
fix recommended is the installation of falcon 0.3.0.1 or 0.3
https://gitlab.com/mailman/postorius/issues/122#note_4509503

If this doesn't help we'll wait till someone more knowledgeable than me
comes along :)

Thanks!

Aditya Divekar
___
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

2016-03-31 Thread Christian Schoepplein
Hi,

On Do, Mär 31, 2016 at 06:39:14 +0530, Aditya Divekar wrote:
>Try removing the /mailman3 part from the URL. i.e. try accessing the URL -
>http://192.168.122.147:8000/

Using this address opens the webinterface for hyperkitty and I could 
browse mailinglist archives, e.g., but what I'd like to do is setup a 
new domain for the new installation.

If I open the settings page directly 
(http://192.168.122.147:8000/mailman3/settings/) I ge tno error, but 
after entering a mail and web host and a description and send the 
formular another error occures :-(.

Seems that something is not correctly installed or configured, but what 
is it?

Ciao and tia,

  Schoepp


signature.asc
Description: Digital signature
___
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

2016-03-31 Thread Aditya Divekar
Hi!

Try removing the /mailman3 part from the URL. i.e. try accessing the URL -
http://192.168.122.147:8000/ 
I'd gotten a similar error. Hope it helps.

Aditya Divekar
___
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] mailman

2016-03-31 Thread Christian Schoepplein

Hi,

I'm getting the following error after a fresh installation of 
mailman_bundler with mailman 3.0.3 included. Is this a known issue or a 
bug? How can I resolve it?


Ciao and thx,

 Schoepp

--
Environment:


Request Method: GET
Request URL: http://192.168.122.147:8000/mailman3/

Django Version: 1.8.11
Python Version: 2.7.9
Installed Applications:
('django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'django.contrib.admin',
 'hyperkitty',
 'social.apps.django_app.default',
 'rest_framework',
 'django_gravatar',
 'crispy_forms',
 'paintstore',
 'compressor',
 'django_browserid',
 'haystack',
 'django_extensions',
 'postorius')
Installed Middleware:
('django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'hyperkitty.middleware.TimezoneMiddleware')


Traceback:
File 
"/opt/mailman-bundler/eggs/Django-1.8.11-py2.7.egg/django/core/handlers/base.py" 
in get_response
  132. response = wrapped_callback(request, 
*callback_args, **callback_kwargs)
File 
"/opt/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py" 
in list_index

  511. lists = sorted(List.objects.all(only_public=only_public),
File 
"/opt/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/models.py" in 
all
  144. objects = getattr(get_client(), 
self.resource_name_plural)
File 
"/opt/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py" 
in lists

  158. response, content = self._connection.call('lists')
File 
"/opt/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py" 
in call
  109. raise HTTPError(url, response.status, content, 
response, None)


Exception Type: HTTPError at /mailman3/
Exception Value: HTTP Error 500: A server error occurred.  Please 
contact the administrator.


signature.asc
Description: Digital signature
___
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