[Mailman-Developers] mailman

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 Ve

Re: [Mailman-Developers] mailman

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-Dev

Re: [Mailman-Developers] mailman

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

Re: [Mailman-Developers] mailman

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

Re: [Mailman-Developers] mailman

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 understan

Re: [Mailman-Developers] mailman

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_bundl

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] mailman

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,

Re: [Mailman-Developers] mailman

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

Re: [Mailman-Developers] mailman

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

Re: [Mailman-Developers] mailman

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... eve

Re: [Mailman-Developers] Correcting the display name in the recipient address

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

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

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. _

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

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 ch