[Mailman-Developers] Re: how to debug Hyperkitty Django Q tasks?
Thank you Steve for your comments, but I am still interested in knowing how Mailman developers would debug issues with Hyperkitty periodic tasks. If no logging is possible for those tasks, I'd consider this as an issue to fix. But I'm not a Python developer and looking at the application from the infrastructure side. So I'm not sure if it's possible or not and if is it an issue or not. I appreciate any clarification you can provide. Danil On Fri, Sep 29, 2023 at 6:30 PM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > Danil Smirnov writes: > > > The issue was initially noticed by a very high load of CPU when > > running periodic tasks. > > I may have seen this but no longer have access to the system where it > happened, and there were other issues so I have no confidence that > the high loads were due to the problem described below. This was > during the initial import of a very large number (~5000) of archives, > and running mailmanweb update_index for the whole thing. The problem > was that with qcluster running, the whole archive indexing and the > periodic indexing stepped on each other's locks. > > We solved this by telling people archive search would be available > randomly over the next few days (ie, when the archiving process > completed that list's archive ;-) and stopping the periodic process > (just renaming the index task in qcluster's queue does this) before > running the index everything task.. > > I suggest doing this to get your archives close to up to date so the > periodic indexing task doesn't get overwhelmed and fail to complete > with its interval. I have no confidence this will solve your problem > completely, but the indexing task may get in the way of solving it. > > I also recommend getting in touch with the Django community as they're > more likely to know things like how to set logging verbosity in these > low-level components. > > Steve > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] how to debug Hyperkitty Django Q tasks?
Hi Mailman developers! We faced an issue with Hyperkitty Django Q tasks and we now trying to deep dive into the technology. The issue was initially noticed by a very high load of CPU when running periodic tasks. There are no errors in any log files (mailmanweb.log and uwsgi-*.log), but if check the web URL http://lists.server.tld/admin/django_q/success/ - there were no successful tasks for a month (all other pages in DJANGO Q section are also empty). We now trying to debug the issue but it seems that the errors which occur in the tasks are not logged anywhere. Adding "DEBUG = True" into the settings_local.py changes nothing and it's not clear how to change the "verbosity" parameter used here: https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_indexes.py?ref_type=heads#L70 Do you have any advice on how to debug those tasks? I appreciate any help you can provide! With kind regards, Danil Smirnov ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: GSoC 2023
Great! Thank you very much for your answer and care. On Wed, Jan 25, 2023 at 5:45 PM Stephen J. Turnbull < stephenjturnb...@gmail.com> wrote: > Danil Smirnov writes: > > > The very promising last year project "List Configuration Tool" seems > wasn't > > completed. > > No, it's done. It's just that the student is a master student who > changed his mind about his future in August, and spent the last few > months polishing applications to PhD programs instead of integrating > his GSoC project. Final presentation of his master thesis is in two > weeks, then I lean on him to do some documentation and a PR. > > All projects from previous years that weren't selected or obsoleted by > ongoing development will be added again when I get around to updating > the ideas page (in practice I just copy last year's and make small > changes), but that's also a couple weeks in the future. > > Steve > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: GSoC 2023
Hi Stephen, The very promising last year project "List Configuration Tool" seems wasn't completed. What is the usual action course in this case? Should it be re-added to the new program? (I hope it won't be buried...) Sincerely, Danil Smirnov On Wed, Jan 25, 2023 at 6:27 AM Stephen J. Turnbull < stephenjturnb...@gmail.com> wrote: > Hi all > > Applications for GSoC 2023 are open and I would like to apply. > Program details: https://summerofcode.withgoogle.com/programs/2023 > You may need to log in with a Google account. > > We could go under the PSF umbrella again (they've applied already), or > we could go it alone. The advantage to the PSF is we can possibly > borrow a mentor from them as we did in 2022 and they'll do some of the > org admin stuff, the advantage to a separate Mailman org is money and > tickets to the Mentor Summit if they do that. There may be other > stuff I haven't thought about. If we decide to apply ourselves but > get cold feet, I suppose we can withdraw without penalty and go with > PSF if we do so a reasonable time before deadline (Feb 8). > > I need some backing from core devs (at least one backup mentor, which > is light work if I'm healthy), but I plan to post to the lists to see > if any of the usual suspects would like to be mentors, too. > > Steve > > ___ > Mailman-Developers mailing list -- mailman-developers@python.org > To unsubscribe send an email to mailman-developers-le...@python.org > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ > Mailman FAQ: https://wiki.list.org/x/AgA3 > > Security Policy: https://wiki.list.org/x/QIA9 > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Regarding willing to contribute to the organization.
Is it allowed to vote here? :) I would passionately vote for the Export-Import feature which is desperately missed. Without this feature for instance it's impossible/too hard to migrate data to another database engine. The issue is https://gitlab.com/mailman/postorius/-/issues/13 пн, 24 янв. 2022 г., 21:27 Sanket Varpe : > Hello, > This is Sanket Varpe, a final year CS student at PICT, Pune. I am looking > to make contributions to open source projects. I have multiple internship > experiences as a backend developer where I architected and implemented > backend of cloud based applications. I am experienced in Javascript, > Node.js, Python, Django etc.I went through mailman projects and found them > very interesting. I went through their issues but as I am little new to > this area I got confused seeing a lot of issues and how to choose one.But > if given a small task/issue or project/new idea to work on at starting > would be very great and i'll definitely make good contributions. Would like > to discuss more if possible. > > Looking forward to hearing from you. > Thank You. > ___ > Mailman-Developers mailing list -- mailman-developers@python.org > To unsubscribe send an email to mailman-developers-le...@python.org > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ > Mailman FAQ: https://wiki.list.org/x/AgA3 > > Security Policy: https://wiki.list.org/x/QIA9 > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Core new release?
On Mon, Jul 5, 2021 at 4:26 AM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > Danil Smirnov writes: > > > Any hope to release a new version soon folks? > > Releases come when they come, you know that. If you want to know what > Abhilash's schedule (if any) is, so that you can plan your own work, > say so. It would help if you could avoid the snark. > Well, this was just a question and not a request or a claim. I'm actually thinking about establishing my own Docker-based releases from master branch, but in this case I would skip participation in beta/pre-release testing due to having my own schedule. Danil ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Core new release?
Any hope to release a new version soon folks? вт, 4 мая 2021 г., 08:13 Abhilash Raj : > > > > On Apr 28, 2021, at 11:03 PM, Danil Smirnov wrote: > > > > Hi, > > > > As per public Gitlab stats for Mailman Core repo, 25 issues have been > > closed in April so far, which is the record of the last 12 months and > beats > > the previous four months total. > > > > From a merge requests perspective, it is the record too, and the merged > > requests number pace is growing by ~15% over the last four months, > reaching > > a quarter of a hundred in April. > > > > I know that it's just a month from the previous Mailman Core release, but > > given the stats above should the next release be planned earlier than > usual? > > A release for Core is actually imminent, but I am not sure about timing as > there > are other things going on. Maybe in two or three weeks I can get some betas > out. > > We want to get out new version of web components soon as they’ve > accumulated > some fixes and new stuff. But the new version of Postorius requires an new > REST > endpoint so we’d need to release Core for that anyway. > > > -- > thanks, > Abhilash Raj (maxking) > > > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Core new release?
Hi, As per public Gitlab stats for Mailman Core repo, 25 issues have been closed in April so far, which is the record of the last 12 months and beats the previous four months total. >From a merge requests perspective, it is the record too, and the merged requests number pace is growing by ~15% over the last four months, reaching a quarter of a hundred in April. I know that it's just a month from the previous Mailman Core release, but given the stats above should the next release be planned earlier than usual? Best regards, Danil Smirnov ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Mailman, postfix and docker
Hey, As promised a while ago, I've prepared Kubernetes PoC for Mailman 3 (Helm chart) which is currently deployed into GCP (GKE Autopilot) and exposed at http://test.mailman4.com/postorius/lists/ The setup is based on Abhilash's container images <https://github.com/maxking/docker-mailman> (up to version 0.3.11 - see below why). Outbound delivery is relayed via Mailgun (due to the outbound port 25 is blocked in GCP), while income emails received by the local Postfix container. When tried previously, ...I've faced only two disappointing issues: 1) HK whitelisting mechanism > which makes no sense in a dynamic Kubernetes environment and 2) a shared > volume, which is needed for Core and Postfix to communicate. The first issue has been resolved by allowing Django's any host notation <https://gitlab.com/mailman/hyperkitty/-/merge_requests/297> (thank you folks!), and the second one I've resolved by myself with help of a sidecar container built from the following code: https://github.com/danil-smirnov/mailman-postfix-extender This solution moves Postfix configuration from file-based to network-based without touching a line of Mailman code. (Of course, it's PoC still and would look much better if it's part of the Mailman 3 codebase, covered by tests, etc.) There are a couple of other issues that I've worked around but have to address to move to a production-grade solution: 1. Hardcoded hostnames issue ( https://github.com/maxking/docker-mailman/issues/449) Worked around by adding some redundant code <https://github.com/danil-smirnov/mailman-helm-chart/blob/main/templates/mailman-web/deployment.yaml#L108-L113> . 2. lmtp_host parameter issue ( https://gitlab.com/mailman/mailman/-/issues/852) Worked around by using IP addresses in postfix_lmtp file (possible up to 0.3.11 version of docker images only - due to recent change <https://github.com/maxking/docker-mailman/commit/c10aa6fce479a78a6c51ac41f0f1f0963bd20d0b#diff-27e621da191f9972846a94828429f1f91d0cdde5cb7ff3c5fe8db38797f2R33> ). The code could be found in this repository: https://github.com/danil-smirnov/mailman-helm-chart I'm glad I've finally shared this, I hope it'll help to improve Mailman 3 compatibility with the modern orchestration tools. With my best regards, Danil Smirnov Mailman3.com On Sun, Dec 20, 2020 at 1:51 PM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > Danil Smirnov writes: > > > Sorry for the confusion - I should write "would allow" instead of > "allows" > > as using socketmap_table would be a great feature but it obviously > requires > > a new endpoint in Mailman core which does not exist yet. > > Ah, OK, so what exists now is the Postfix docker (which you provided a > reference). > > > Otherwise everything looks fine and with those two issues > > resolved/mitigated there is no problem to deploy Mailman 3 in > Kubernetes, I > > can prepare an example Helm chart for it. > > That would be great! > > Steve > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Hyperkitty's ability to build a thread
Hi everyone and Abhilash in particular :) I've faced a case when Hypirkitty is unable to chain messages into a thread: https://wlug.mailman3.com/hyperkitty/list/w...@lists.wlug.org/ (See messages with the subject "WLUG Meeting Feb 11th 2021! Topic: Good question!".) It's a quite disappointment as GMail does show them correctly - as a single thread. As per my small investigation, a subscriber Robert N. Evans seems to have "In-Reply-To" headers stripped from the messages that probably causes the thread to break. I wonder if Hyperkitty is able to leverage some other method to combine the thread correctly in this case? "Good" and "bad" message examples are in the attachment. Best regards, Danil Smirnov --- Begin Message --- John Stoffel via WLUG writes: > I recall, it's mostly the memory ordering around byte accesses that > are the problem. Are you saying that the Big Endian vs Little Endian flame war actually had consequences in the Real World? Or something even more obscure? -- Keith ___ WLUG mailing list -- w...@lists.wlug.org To unsubscribe send an email to wlug-le...@lists.wlug.org Create Account: https://wlug.mailman3.com/accounts/signup/ Change Settings: https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ Web Forum/Archive: https://wlug.mailman3.com/hyperkitty/list/w...@lists.wlug.org/message/3LQYE4JHDJ7YLZX6EST7S4D4Z3KXGE3T/ --- End Message --- --- Begin Message --- That is not what I see when I query one of the major name servers. I would guess your server is configured differently... rne@P5:~$ dig @1.1.1.1 isc.org ; <<>> DiG 9.16.1-Ubuntu <<>> @1.1.1.1 isc.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31866 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;isc.org. IN A ;; ANSWER SECTION: isc.org.9 IN A 149.20.1.66 ;; Query time: 24 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Feb 11 10:03:30 EST 2021 ;; MSG SIZE rcvd: 52 -BE -Original Message- >From: Keith Wright via WLUG >Sent: Feb 11, 2021 1:04 AM >To: Worcester Linux Users' Group General Discussion >Cc: w...@lists.wlug.org, andre.lehov...@gmx.com, Keith Wright > >Subject: [WLUG] Re: WLUG Meeting Feb 11th 2021! Topic: Good question! > >Andre Lehovich via WLUG writes: > >>> dig @66.92.74.188 isc.org >> >> Here you go, hope it's useful... > >Thank you. That's a lot of information. > >> quetzal:~ al$ dig @66.92.74.188 isc.org >> >> ; <<>> DiG 9.10.6 <<>> @66.92.74.188 isc.org >> ; (1 server found) >> ;; global options: +cmd >> ;; Got answer: >> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11995 >> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 27 >> ;; WARNING: recursion requested but not available > ^ ^ ^^^ ^^^ ^ >That looks good. >I don't want to be doing recursion for you (nothing personal). > >But where did all the rest of that come from? >I've never seen anything like that! >Did my server send all that? Why?? > >> ;; OPT PSEUDOSECTION: >> ; EDNS: version: 0, flags:; udp: 4096 >> ;; QUESTION SECTION: >> ;isc.org.INA >> >> ;; AUTHORITY SECTION: >> .348191INNSc.root-servers.net. >> .348191INNSd.root-servers.net. >> .348191INNSe.root-servers.net. >> .348191INNSf.root-servers.net. >> .348191INNSg.root-servers.net. >> .348191INNSh.root-servers.net. >> .348191INNSi.root-servers.net. >> .348191INNSj.root-servers.net. >> .348191INNSk.root-servers.net. >> .348191INNSl.root-servers.net. >> .348191INNSm.root-servers.net. >> .348191INNSa.root-servers.net. >> .348191INNSb.root-servers.net. >> >> ;; ADDITIONAL SECTION: >> a.root-servers.net.348191INA198.41.0.4 >> a.root-servers.net.348191IN2001:503:ba3e::2:30 >> b.root-servers.net.348191INA199.9.14.201 >> b.root-servers.net.348191IN2001:500:200::b >> c.root-servers.net.348191INA192.33.4.12 >> c.root-servers.net.348191IN2001:500:2::c >> d.root-servers.net.
[Mailman-Developers] Re: Mailman, postfix and docker
Hey Steve, вс, 20 дек. 2020 г., 6:03 Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp>: > Danil Smirnov writes: > > > But how about that idea to offload Postfix-Mailman communication from a > > filesystem to a network using Postfix socketmap_tables feature which I > like > > a lot as it allows me to get rid of using any shared volumes in the > stack > > completely - it's quite convenient in multi-host setups like Docker > Swarm > > or Kubernetes... > > Would you be willing to write up a description of your configuration > that we can add to the wiki and/or documentation? Communication in > multihost setups, especially those intended to isolate hosts exposed > to the internet from the intranet, is a sore point for us since > Mailman 3 is really designed as a single-host, three application > system. Sorry for the confusion - I should write "would allow" instead of "allows" as using socketmap_table would be a great feature but it obviously requires a new endpoint in Mailman core which does not exist yet. I've experimented a lot with Mailman 3 in Kubernetes and I've faced only two disappointing issues: 1) HK whitelisting mechanism <https://gitlab.com/mailman/hyperkitty/-/issues/18> which makes no sense in a dynamic Kubernetes environment and 2) a shared volume, which is needed for Core and Postfix to communicate. Otherwise everything looks fine and with those two issues resolved/mitigated there is no problem to deploy Mailman 3 in Kubernetes, I can prepare an example Helm chart for it. Danil ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Mailman, postfix and docker
Hi Hans-Martin, On Sat, Dec 19, 2020 at 1:05 PM Hans-Martin Mosner wrote: > We're currently working on moving our mail system over to a "mailu" > dockerized implementation, so I will gather some > experience in connecting Mailman3 with a dockerized postfix. > Yeah, using dockerised postfix is straight-forward in the same docker-compose stack - one just need to mount var/data folder of Mailman core into the Postfix container, set transport_maps, local_recipient_maps and relay_domains parameters to correct values and set Postfix service name into SMTP_HOST environment variable of Core and Web services. (I'm using my simple Postfix Docker image for this purpose - works pretty well: https://hub.docker.com/r/danilsmirnov/postfix ) But how about that idea to offload Postfix-Mailman communication from a filesystem to a network using Postfix socketmap_tables feature which I like a lot as it allows me to get rid of using any shared volumes in the stack completely - it's quite convenient in multi-host setups like Docker Swarm or Kubernetes... Best regards, Danil ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Docker files for mailman
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 python-virtualenv ruby-sass").
I'm not sure whether I need to change it in the Wiki...
On 18 November 2016 at 16:08, Danil Smirnov <da...@smirnov.la> wrote:
> Hi Simon!
>
> I've just tried to build docker image from the Dockerfile mentioned on page
> https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile
>
> The building has stopped with the following error
>
> Installing mailman.
>> The executable python3.4 (from --python=python3.4) does not exist
>> /tmp/tmpez1ftK/run: 2: /tmp/tmpez1ftK/run:
>> /mailman3/mailman-bundler/venv-3.4/bin/pip:
>> not found
>> While:
>> Installing mailman.
>>
>> An internal error occurred due to a bug in either zc.buildout or in a
>> recipe being used:
>> Traceback (most recent call last):
>> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py",
>> line 1995, in main
>> getattr(buildout, command)(args)
>> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py",
>> line 666, in install
>> installed_files = self[part]._call(recipe.install)
>> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py",
>> line 1410, in _call
>> return f()
>> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0.
>> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install
>> self.execute()
>> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0.
>> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute
>> run_commands(cmds, self.shell)
>> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0.
>> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands
>> check_call('%s %s' % (shell, tmpfile), shell=True)
>> File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
>> raise CalledProcessError(retcode, cmd)
>> CalledProcessError: Command 'sh /tmp/tmpez1ftK/run' returned non-zero
>> exit status 127
>> The command '/bin/sh -c buildout' returned a non-zero code: 1
>>
>
> Do you have any clue what happens?
>
> Danil
>
>
> On 17 July 2016 at 20:06, Simon Hanna <simon.ha...@serve-me.info> wrote:
>
>> Hi,
>>
>> I started working on docker files for Mailman.
>>
>> I created three repositories:
>> - https://github.com/simonsmiley/postorius-docker
>> Holds the files needed to create a postorius container
>> - https://github.com/simonsmiley/mailman-docker
>> Holds the files needed to create a core container
>> - https://github.com/simonsmiley/mailman-compose
>> Holds docker-compose files that greatly simply the process of running
>> the containers
>>
>> * The mailman repo currently lacks documentation
>> * Currently no emails can be sent.
>> I still have to figure out what the best way is...
>> * Hyperkitty will be added next
>> (together with a complete "bundler" install)
>>
>>
>> I pushed two images to the docker hub. Their names are
>> thelinuxguy/postorius and thelinuxguy/mailman
>>
>> I created two organizations
>> mailman on docker hub and gnu-mailman on github
>> https://github.com/gnu-mailman
>> https://hub.docker.com/u/mailman/
>>
>> I know we shouldn't use github, but there is no way around
>> github/bitbucket for automated builds on docker hub.
>>
>> I post here to inform you about the docker images and I also to ask if
>> I'm allowed to keep these two organizations and move my images/repos
>> there. I'll happily give push/owner access to additional people if
>> requested.
>>
>> The repositories could be mirrored to the gitlab mailman group,
>> sadly the process doesn't work the other way round just yet.
>>
>> In case this request gets denied, I'll just remove the organizations and
>> let the images be "unofficial".
>>
>> cheers,
>> Simon
>> ___
>> 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/ma
>> ilman-developers%40python.org/
>> Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/
>> danil%40smirnov.la
>>
>> 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] can't login with Google/Yahoo (last mailman-bundler)
I'm sorry if it's not right place to ask for the support but there is no
information regarding the issue in Google as well as
mailman-dev/mailman-user lists. So I'm stale in the issue and have no idea
what to do. If you can give me just a direction to dig, it would be very
helpful...
2016-02-17 14:36 GMT+02:00 Danil Smirnov <da...@smirnov.la>:
> I suspect I need to add my httpd configuration:
>
> ---
>
>
> SuexecUserGroup "#500" "#500"
> ServerName lists.domain.tld
> ServerAlias www.lists.domain.tld
> ServerAlias webmail.lists.domain.tld
> ServerAlias admin.lists.domain.tld
> DocumentRoot /home/mailman3/domains/lists.domain.tld/public_html
> ErrorLog /var/log/virtualmin/lists.domain.tld_error_log
> CustomLog /var/log/virtualmin/lists.domain.tld_access_log combined
> ScriptAlias /cgi-bin/ /home/mailman3/domains/lists.domain.tld/cgi-bin/
> ScriptAlias /awstats/ /home/mailman3/domains/lists.domain.tld/cgi-bin/
> DirectoryIndex index.html index.htm index.php index.php4 index.php5
>
> Options -Indexes +IncludesNOEXEC +SymLinksIfOwnerMatch +ExecCGI
> allow from all
> AllowOverride All
> Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch
> Require all granted
> AddType application/x-httpd-php .php
> AddHandler fcgid-script .php
> AddHandler fcgid-script .php5
> FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi .php
> FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi
> .php5
>
>
> allow from all
> AllowOverride All
> Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch
> Require all granted
>
> RewriteEngine on
> RewriteCond %{HTTP_HOST} =webmail.lists.domain.tld
> RewriteRule ^(.*) https://lists.domain.tld:2/ [R]
> RewriteCond %{HTTP_HOST} =admin.lists.domain.tld
> RewriteRule ^(.*) https://lists.domain.tld:1/ [R]
> RemoveHandler .php
> RemoveHandler .php5
> php_admin_value engine Off
> IPCCommTimeout 31
> FcgidMaxRequestLen 1073741824
>
> AuthName "lists.domain.tld statistics"
> AuthType Basic
> AuthUserFile /home/mailman3/domains/lists.domain.tld/.awstats-htpasswd
> require valid-user
>
>
> # Here, use the value of the STATIC_ROOT variable in your Django
> configuration file (production.py)
> Alias /robots.txt /var/spool/mailman-web/static/hyperkitty/robots.txt
> Alias /favicon.ico /var/spool/mailman-web/static/hyperkitty/favicon.ico
> Alias /static /var/spool/mailman-web/static
>
> Order deny,allow
> Allow from all
> Require all granted
>
>
> #ErrorLog /var/log/httpd/mailman-web_error.log
> #CustomLog /var/log/httpd/mailman-web_access.log combined
>
> WSGIScriptAlias / /usr/local/src/mailman-bundler/bin/mailman-web.wsgi
> WSGIDaemonProcess mailman-web display-name=mailman-web
> maximum-requests=1000 processes=4 threads=4
> python-path=/usr/local/src/venv/lib/python2.7/site-packages
>
>
>
> Order deny,allow
> Allow from all
> Require all granted
>
> WSGIProcessGroup mailman-web
>
>
>
> ---
>
> 2016-02-17 13:48 GMT+02:00 Danil Smirnov <da...@smirnov.la>:
>
>> Hi devs!
>>
>> I'm still need your advices...
>> Now I have the following errors when trying to authenticate with Google
>> or Yahoo:
>>
>> ---
>> ERROR 2016-02-17 05:40:44,363 base 1690 139772999759616 Internal Server
>> Error: /login/google/
>> Traceback (most recent call last):
>> File
>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py",
>> line 132, in get_response
>> response = wrapped_callback(request, *callback_args,
>> **callback_kwargs)
>> File
>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/views/decorators/cache.py",
>> line 57, in _wrapped_view_func
>> response = view_func(request, *args, **kwargs)
>> File
>> "/usr/local/src/venv/lib/python2.7/site-packages/social/apps/django_app/utils.py",
>> line 51, in wrapper
>> return func(request, backend, *args, **kwargs)
>> TypeError: auth() got an unexpected keyword argument 'SSL'
>> ---
>>
>> Please advice how to manage this...
>>
>> Danil
>>
>
>
___
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] can't login with Google/Yahoo (last mailman-bundler)
I suspect I need to add my httpd configuration:
---
SuexecUserGroup "#500" "#500"
ServerName lists.domain.tld
ServerAlias www.lists.domain.tld
ServerAlias webmail.lists.domain.tld
ServerAlias admin.lists.domain.tld
DocumentRoot /home/mailman3/domains/lists.domain.tld/public_html
ErrorLog /var/log/virtualmin/lists.domain.tld_error_log
CustomLog /var/log/virtualmin/lists.domain.tld_access_log combined
ScriptAlias /cgi-bin/ /home/mailman3/domains/lists.domain.tld/cgi-bin/
ScriptAlias /awstats/ /home/mailman3/domains/lists.domain.tld/cgi-bin/
DirectoryIndex index.html index.htm index.php index.php4 index.php5
Options -Indexes +IncludesNOEXEC +SymLinksIfOwnerMatch +ExecCGI
allow from all
AllowOverride All
Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch
Require all granted
AddType application/x-httpd-php .php
AddHandler fcgid-script .php
AddHandler fcgid-script .php5
FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi .php
FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi .php5
allow from all
AllowOverride All
Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch
Require all granted
RewriteEngine on
RewriteCond %{HTTP_HOST} =webmail.lists.domain.tld
RewriteRule ^(.*) https://lists.domain.tld:2/ [R]
RewriteCond %{HTTP_HOST} =admin.lists.domain.tld
RewriteRule ^(.*) https://lists.domain.tld:1/ [R]
RemoveHandler .php
RemoveHandler .php5
php_admin_value engine Off
IPCCommTimeout 31
FcgidMaxRequestLen 1073741824
AuthName "lists.domain.tld statistics"
AuthType Basic
AuthUserFile /home/mailman3/domains/lists.domain.tld/.awstats-htpasswd
require valid-user
# Here, use the value of the STATIC_ROOT variable in your Django
configuration file (production.py)
Alias /robots.txt /var/spool/mailman-web/static/hyperkitty/robots.txt
Alias /favicon.ico /var/spool/mailman-web/static/hyperkitty/favicon.ico
Alias /static /var/spool/mailman-web/static
Order deny,allow
Allow from all
Require all granted
#ErrorLog /var/log/httpd/mailman-web_error.log
#CustomLog /var/log/httpd/mailman-web_access.log combined
WSGIScriptAlias / /usr/local/src/mailman-bundler/bin/mailman-web.wsgi
WSGIDaemonProcess mailman-web display-name=mailman-web
maximum-requests=1000 processes=4 threads=4
python-path=/usr/local/src/venv/lib/python2.7/site-packages
Order deny,allow
Allow from all
Require all granted
WSGIProcessGroup mailman-web
---
2016-02-17 13:48 GMT+02:00 Danil Smirnov <da...@smirnov.la>:
> Hi devs!
>
> I'm still need your advices...
> Now I have the following errors when trying to authenticate with Google or
> Yahoo:
>
> ---
> ERROR 2016-02-17 05:40:44,363 base 1690 139772999759616 Internal Server
> Error: /login/google/
> Traceback (most recent call last):
> File
> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py",
> line 132, in get_response
> response = wrapped_callback(request, *callback_args, **callback_kwargs)
> File
> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/views/decorators/cache.py",
> line 57, in _wrapped_view_func
> response = view_func(request, *args, **kwargs)
> File
> "/usr/local/src/venv/lib/python2.7/site-packages/social/apps/django_app/utils.py",
> line 51, in wrapper
> return func(request, backend, *args, **kwargs)
> TypeError: auth() got an unexpected keyword argument 'SSL'
> ---
>
> Please advice how to manage this...
>
> Danil
>
___
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] can't login with Google/Yahoo (last mailman-bundler)
Hi devs! I'm still need your advices... Now I have the following errors when trying to authenticate with Google or Yahoo: --- ERROR 2016-02-17 05:40:44,363 base 1690 139772999759616 Internal Server Error: /login/google/ Traceback (most recent call last): File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/views/decorators/cache.py", line 57, in _wrapped_view_func response = view_func(request, *args, **kwargs) File "/usr/local/src/venv/lib/python2.7/site-packages/social/apps/django_app/utils.py", line 51, in wrapper return func(request, backend, *args, **kwargs) TypeError: auth() got an unexpected keyword argument 'SSL' --- Please advice how to manage this... Danil ___ 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] OfflineGenerationError after mailman-bundler install
The error was gone after several reconfigurations/reboots. Still have no idea what it was... 2016-02-17 12:22 GMT+02:00 Danil Smirnov <da...@smirnov.la>: > Sorry again, but the error returns after several page refresh - weird, but > it looks like not every opening of the page cause the error! > > 2016-02-17 12:12 GMT+02:00 Danil Smirnov <da...@smirnov.la>: > >> The error was fixed by bin/mailman-post-update, sorry. >> >> 2016-02-17 11:55 GMT+02:00 Danil Smirnov <da...@smirnov.la>: >> >>> Hi everybody! >>> >>> After installing last mailman-bundler I've got the following in the >>> Hyperkitty logs: >>> >>> ERROR 2016-02-17 03:42:03,804 base 1762 140633939375872 Internal Server >>> Error: /archives/ >>> Traceback (most recent call last): >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", >>> line 132, in get_response >>> response = wrapped_callback(request, *callback_args, >>> **callback_kwargs) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/hyperkitty/views/index.py", >>> line 76, in index >>> return render(request, "hyperkitty/index.html", context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/shortcuts.py", >>> line 67, in render >>> template_name, context, request=request, using=using) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader.py", >>> line 99, in render_to_string >>> return template.render(context, request) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/backends/django.py", >>> line 74, in render >>> return self.template.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 210, in render >>> return self._render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 202, in _render >>> return self.nodelist.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 905, in render >>> bit = self.render_node(node, context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 919, in render_node >>> return node.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader_tags.py", >>> line 135, in render >>> return compiled_parent._render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 202, in _render >>> return self.nodelist.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 905, in render >>> bit = self.render_node(node, context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 919, in render_node >>> return node.render(context) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >>> line 127, in render >>> return self.render_compressed(context, self.kind, self.mode, >>> forced=forced) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >>> line 86, in render_compressed >>> return self.render_offline(context) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >>> line 71, in render_offline >>> 'You may need to run "python manage.py compress".' % key) >>> OfflineGenerationError: You have offline compression enabled but key >>> "57d3e0fcad3f7e67ac65637e9475af43" is missing from offline manifest. You >>> may need to run "python manage.py compress". >>> >>> Please advice how to fix this error properly. >>> >>> Danil >>> >> >> > ___ 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] OfflineGenerationError after mailman-bundler install
Sorry again, but the error returns after several page refresh - weird, but it looks like not every opening of the page cause the error! 2016-02-17 12:12 GMT+02:00 Danil Smirnov <da...@smirnov.la>: > The error was fixed by bin/mailman-post-update, sorry. > > 2016-02-17 11:55 GMT+02:00 Danil Smirnov <da...@smirnov.la>: > >> Hi everybody! >> >> After installing last mailman-bundler I've got the following in the >> Hyperkitty logs: >> >> ERROR 2016-02-17 03:42:03,804 base 1762 140633939375872 Internal Server >> Error: /archives/ >> Traceback (most recent call last): >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", >> line 132, in get_response >> response = wrapped_callback(request, *callback_args, >> **callback_kwargs) >> File >> "/usr/local/src/venv/lib/python2.7/site-packages/hyperkitty/views/index.py", >> line 76, in index >> return render(request, "hyperkitty/index.html", context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/shortcuts.py", >> line 67, in render >> template_name, context, request=request, using=using) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader.py", >> line 99, in render_to_string >> return template.render(context, request) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/backends/django.py", >> line 74, in render >> return self.template.render(context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 210, in render >> return self._render(context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 202, in _render >> return self.nodelist.render(context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 905, in render >> bit = self.render_node(node, context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 919, in render_node >> return node.render(context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader_tags.py", >> line 135, in render >> return compiled_parent._render(context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 202, in _render >> return self.nodelist.render(context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 905, in render >> bit = self.render_node(node, context) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >> line 919, in render_node >> return node.render(context) >> File >> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >> line 127, in render >> return self.render_compressed(context, self.kind, self.mode, >> forced=forced) >> File >> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >> line 86, in render_compressed >> return self.render_offline(context) >> File >> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >> line 71, in render_offline >> 'You may need to run "python manage.py compress".' % key) >> OfflineGenerationError: You have offline compression enabled but key >> "57d3e0fcad3f7e67ac65637e9475af43" is missing from offline manifest. You >> may need to run "python manage.py compress". >> >> Please advice how to fix this error properly. >> >> Danil >> > > ___ 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] OfflineGenerationError after mailman-bundler install
The error was fixed by bin/mailman-post-update, sorry. 2016-02-17 11:55 GMT+02:00 Danil Smirnov <da...@smirnov.la>: > Hi everybody! > > After installing last mailman-bundler I've got the following in the > Hyperkitty logs: > > ERROR 2016-02-17 03:42:03,804 base 1762 140633939375872 Internal Server > Error: /archives/ > Traceback (most recent call last): > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", > line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File > "/usr/local/src/venv/lib/python2.7/site-packages/hyperkitty/views/index.py", > line 76, in index > return render(request, "hyperkitty/index.html", context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/shortcuts.py", > line 67, in render > template_name, context, request=request, using=using) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader.py", > line 99, in render_to_string > return template.render(context, request) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/backends/django.py", > line 74, in render > return self.template.render(context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 210, in render > return self._render(context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 202, in _render > return self.nodelist.render(context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 905, in render > bit = self.render_node(node, context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 919, in render_node > return node.render(context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader_tags.py", > line 135, in render > return compiled_parent._render(context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 202, in _render > return self.nodelist.render(context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 905, in render > bit = self.render_node(node, context) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", > line 919, in render_node > return node.render(context) > File > "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", > line 127, in render > return self.render_compressed(context, self.kind, self.mode, > forced=forced) > File > "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", > line 86, in render_compressed > return self.render_offline(context) > File > "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", > line 71, in render_offline > 'You may need to run "python manage.py compress".' % key) > OfflineGenerationError: You have offline compression enabled but key > "57d3e0fcad3f7e67ac65637e9475af43" is missing from offline manifest. You > may need to run "python manage.py compress". > > Please advice how to fix this error properly. > > Danil > ___ 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] OfflineGenerationError after mailman-bundler install
Hi everybody! After installing last mailman-bundler I've got the following in the Hyperkitty logs: ERROR 2016-02-17 03:42:03,804 base 1762 140633939375872 Internal Server Error: /archives/ Traceback (most recent call last): File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/src/venv/lib/python2.7/site-packages/hyperkitty/views/index.py", line 76, in index return render(request, "hyperkitty/index.html", context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/shortcuts.py", line 67, in render template_name, context, request=request, using=using) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader.py", line 99, in render_to_string return template.render(context, request) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/backends/django.py", line 74, in render return self.template.render(context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 210, in render return self._render(context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 202, in _render return self.nodelist.render(context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 905, in render bit = self.render_node(node, context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 919, in render_node return node.render(context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader_tags.py", line 135, in render return compiled_parent._render(context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 202, in _render return self.nodelist.render(context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 905, in render bit = self.render_node(node, context) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", line 919, in render_node return node.render(context) File "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 127, in render return self.render_compressed(context, self.kind, self.mode, forced=forced) File "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 86, in render_compressed return self.render_offline(context) File "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 71, in render_offline 'You may need to run "python manage.py compress".' % key) OfflineGenerationError: You have offline compression enabled but key "57d3e0fcad3f7e67ac65637e9475af43" is missing from offline manifest. You may need to run "python manage.py compress". Please advice how to fix this error properly. Danil ___ 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 3 status
Thank you for your observation, Stephen! 2015-07-13 4:47 GMT+03:00 Stephen J. Turnbull step...@xemacs.org: What Mailman 3 lacks so far --- - The topics feature. - Ports of most Mailman 2 add-ons and commonly-used patches. Do I correctly understand that Mailman 3 also does not include Usenet gateway support yet? Danil ___ 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 3 upgrade WAS: Re: postorius login question
2015-06-08 12:22 GMT+03:00 Aurelien Bompard aurel...@bompard.org: I fixed it in HyperKitty and released a new tarballs a few days later, it should be OK but it's not officially supported for 3.0. There are a few missing features, like password reset, etc. To login with the internal database, set USE_INTERNAL_AUTH to True in your settings file. Thank you Aurelien! Could you please give us some details regarding the right way of upgrade of Mailman 3? We have good installation manual but there are lack of information regarding the upgrade process. It's important to have one because of the current development stage is pretty dynamic. Best, Danil ___ 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] html question
2015-06-08 11:43 GMT+03:00 Abhilash Raj raj.abhila...@gmail.com: Care to open an issue for it on Gitlab? https://gitlab.com/mailman/postorius/issues Done: https://gitlab.com/mailman/postorius/issues/23 ___ 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] virtual hosts again
Hi! Are there a way to install Mailman 3 on several virtual hosts to make Postorius archives be generated separately for each of them? (Or, at least, to use several aliases for them like 'lists.domain.tld' for each domain added.) I would like to know the right way to do this (if it's possible). Now I'm stuck with one virtual host configured for Postorius and could not add another one. Danil ___ 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] postorius login question
Hi Mailman3 devs! When I click on Login link on Postorius main page http://lists.domain.tld/archives/ I get the page with the following login methods: Mozilla Persona Google Yahoo! Above these three links I see words Login with your email which is not link and this is confusing. Are there a way to login with just email and password as we have in Mailman2? Danil ___ 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] MM 3: bundler; stuck on buildout phase...
2015-06-05 4:16 GMT+03:00 bill.co...@unh.edu: Full buildout log attached. Any suggestions on how to proceed would be welcomed. Do pip install python-social-auth Best, Danil ___ 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] can not post to the list
2015-06-03 11:17 GMT+03:00 Aurelien Bompard aurel...@bompard.org:
If the first URL does not match, it means that HyperKitty is not
activated in the virtualhost for 127.0.0.1.
You should get a message in HyperKitty's logs stating that the
connection was refused because the IP address is not allowed.
You have two options:
- activate HyperKitty for 127.0.0.1
- in HyperKitty's settings file (production.py), edit the
MAILMAN_ARCHIVER_FROM variable to allow you local IP. This IP address
must not change.
Thank you, Aurelian. Now I'm figured all these out.
The first option - to activate Hyperkitty on 127.0.0.1 is not good
opportunity for me because I have shared host and would not have
Mailman 3 archive/manager on every domain I have there instead of its
actual content. :)
Below is the instruction how you would configure Mailman3 just for one
virtual host of your server.
1. Put content of deployment/apache.conf into the virtualhost section
of your Mailman 3 archive/manager domain - every line excluding the
following 4 ones:
WSGISocketPrefix run/wsgi
WSGIRestrictStdout On
WSGIRestrictSignal Off
WSGIPythonOptimize 1
You must put them outside of any of your virtualhost section.
2. Edit your deployment/mailman-hyperkitty.cfg file and set
base_url: http://yourvirtualhostdomain.tld/archives
3. Add to your mailman_web/settings_local.py the ip address of your
virtual host:
MAILMAN_ARCHIVER_FROM = ('ip.ip.ip.ip')
I hope this will help someone.
Everybody have a great weekend,
Danil
___
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] can not post to the list
Could you please be more specific with this activate Hyperkytty on ...? Link to the manual would be okay... (Sorry for the topposting). 03.06.2015 11:18 пользователь Aurelien Bompard aurel...@bompard.org написал: Probably last one is because of misconfiguration of api_key: SecretArchiverAPIKey ? If the first URL does not match, it means that HyperKitty is not activated in the virtualhost for 127.0.0.1. You should get a message in HyperKitty's logs stating that the connection was refused because the IP address is not allowed. You have two options: - activate HyperKitty for 127.0.0.1 - in HyperKitty's settings file (production.py), edit the MAILMAN_ARCHIVER_FROM variable to allow you local IP. This IP address must not change. Aurélien ___ 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/danil%40smirnov.la 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] right adding of mailman 3 conf lines to httpd.conf
2015-06-01 12:17 GMT+03:00 Aurelien Bompard aurel...@bompard.org: Ah, right, the fact that you have to create the directory and set the permissions for the production setup was not added in the README file. I'll fix that. I'm however surprised that you didn't get the error in your Apache logs without uncommenting the ErrorLog directive. Do you have anything in your apache error log? Thanks Aurelien! I've checked one more time - no, I have nothing related to the issue in httpd logs. Danil ___ 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 3: http vs https
Please help I've got in troubles with http/https schemes of the Postorious/Hyperkitty. Initially I configured Mailman 3 in :443 virtualhost section of subdomain lists.domaint.tld with automatic redirection from :80 by mod_rewrite. I could access pages with https scheme. Then I noticed that my SSL-certificate doesn't allow wildcard-subdomains. I saw two options here: 1) To use a folder on main domain.tld instead of subdomain which does not looks like a great idea because of Hyperkitty somehow control robots.txt file which is domain-wide, not folder-wide. 2) To get rid of https. I choose last option and have moved Mailman 3 config lines to :80 virtualhost, commented redirection too. Now I can see Postorius and Hyperkitty on http connection but I can't login - I've been redirecting to https pages right after login, which are not accessible. The worst thing is that if I move Mailman 3 lines back to :443 virtualhost section, I got unbelievable redirect from https site to http one which was never configured! So I messed up completely. Danil p.s. I use 'Forget about site' feature of Firefox browser and check with Chrome so it's unlikely a cache issue. ___ 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] can not post to the list
2015-06-01 12:27 GMT+03:00 Aurelien Bompard aurel...@bompard.org: That's Mailman core trying to talk to HyperKitty over http to get the list archives URL. The URL it's trying to reach is set in the deployment/mailman-hyperkitty.cfg. My guess is that you need to update it because if HyperKitty is running under Apache, the port is no longer 8000, it's 80 (so you can remove it from the URL). If that's the problem, I'll update the README file. Thanks, Aurelien. I tried two variants in mailman-hyperkitty.cfg: base_url: http://127.0.0.1/archives -- Jun 01 21:15:55 2015 (17357) held message approved, message-id: CAMrrXbrjXySQCuW21zOSMrV=hfypqoddx95jm-kexzqidcs...@mail.gmail.com Jun 01 21:15:55 2015 (17357) 127.0.0.1 - - POST /3.0/lists/t...@domain.tld/held/6 HTTP/1.1 204 0 Jun 01 21:15:56 2015 (17364) HyperKitty failure on http://127.0.0.1/archives/api/mailman/urls: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title404 Not Found/title /headbody h1Not Found/h1 pThe requested URL /archives/api/mailman/urls was not found on this server./p /body/html (404) Jun 01 21:15:56 2015 (17364) HyperKitty failure on http://127.0.0.1/archives/api/mailman/urls: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title404 Not Found/title /headbody h1Not Found/h1 pThe requested URL /archives/api/mailman/urls was not found on this server./p /body/html (404) Jun 01 21:15:56 2015 (17365) HyperKitty failure on http://127.0.0.1/archives/api/mailman/archive: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title404 Not Found/title /headbody h1Not Found/h1 pThe requested URL /archives/api/mailman/archive was not found on this server./p /body/html (404) Jun 01 21:15:56 2015 (17365) Broken archiver: hyperkitty Traceback (most recent call last): File /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/archive.py, line 107, in _dispose archiver.system_archiver.archive_message(mlist, msg_copy) File /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py, line 132, in archive_message raise ValueError(result.text) ValueError: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title404 Not Found/title /headbody h1Not Found/h1 pThe requested URL /archives/api/mailman/archive was not found on this server./p /body/html -- base_url: http://lists.domain.tld/archives -- Jun 01 21:09:54 2015 (17357) held message approved, message-id: camrrxbqtf2d-5babmq3dmvh34xwuksaqkdtkotzwmvtb5dd...@mail.gmail.com Jun 01 21:09:54 2015 (17357) 127.0.0.1 - - POST /3.0/lists/t...@domain.tld/held/5 HTTP/1.1 204 0 Jun 01 21:09:55 2015 (17357) 127.0.0.1 - - GET /3.0/lists/test.domain.tld HTTP/1.1 200 303 Jun 01 21:09:55 2015 (17357) 127.0.0.1 - - GET /3.0/lists/t...@domain.tld/held HTTP/1.1 200 90 Jun 01 21:09:55 2015 (17364) HyperKitty failure on http://lists.domain.tld/archives/api/mailman/urls: htmltitleForbidden/titlebody h1Access is forbidden/h1/body/html (403) Jun 01 21:09:55 2015 (17364) HyperKitty failure on http://lists.domain.tld/archives/api/mailman/urls: htmltitleForbidden/titlebody h1Access is forbidden/h1/body/html (403) Jun 01 21:09:56 2015 (17365) HyperKitty failure on http://lists.domain.tld/archives/api/mailman/archive: htmltitleForbidden/titlebody h1Access is forbidden/h1/body/html (403) Jun 01 21:09:56 2015 (17365) Broken archiver: hyperkitty Traceback (most recent call last): File /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/archive.py, line 107, in _dispose archiver.system_archiver.archive_message(mlist, msg_copy) File /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py, line 132, in archive_message raise ValueError(result.text) ValueError: htmltitleForbidden/titlebody h1Access is forbidden/h1/body/html -- Probably last one is because of misconfiguration of api_key: SecretArchiverAPIKey ? What should I put here? Danil ___ 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 3: http vs https
2015-06-01 17:23 GMT+03:00 Aurelien Bompard aurel...@bompard.org: If you don't want to use HTTPS, there's a USE_SSL variable in the Django settings file that you need to set to False. Thanks, this works. ___ 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] Recipient address rejected: User unknown in virtual alias table
2015-05-30 1:21 GMT+03:00 Barry Warsaw ba...@list.org: It sounds like a Postfix problem, so cranking up Postfix logging is probably going to be the most fruitful avenue. I understand this, of course this is the postfix issue, I see the error in maiillog: May 30 00:50:03 host postfix/smtpd[5062]: NOQUEUE: reject: RCPT from mail-wg0-f46.google.com[74.125.82.46]: 550 5.1.1 test-ow...@domain.tld: Recipient address rejected: User unknown in virtual alias table; from=danil.smir...@gmail.com to=test-ow...@domain.tld proto=ESMTP helo=mail-wg0-f46.google.com But I have everything required by installation manual in the main.conf so I have no idea what going wrong and how to debug this wrong alias problem. Any advice? Danil ___ 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] Recipient address rejected: User unknown in virtual alias table
2015-05-30 9:02 GMT+03:00 Danil Smirnov da...@smirnov.la: But I have everything required by installation manual in the main.conf so I have no idea what going wrong and how to debug this wrong alias problem. Found postfix misconfiguration. Have no relation to Mailman 3. Just forget about this. Danil ___ 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] can not post to the list
I have Mailman 3 installed and Postorius and Hyperkitty seemingly working.
I can subscribe, get welcome message and when I send message to the
list it appears in held messages.
Then when I accept the message, it does not come into the list and
does not appear in the archives.
Here what I found in the logs:
---
May 30 09:15:30 2015 (2247) held message approved, message-id:
CAMrrXbpHaUbHvw7y6TSkhQxG2fLqEpz_TUXpZHwi=zxyplz...@mail.gmail.com
May 30 09:15:30 2015 (2247) 127.0.0.1 - - POST
/3.0/lists/t...@domain.tld/held/2 HTTP/1.1 204 0
May 30 09:15:30 2015 (2247) 127.0.0.1 - - GET
/3.0/lists/test.domain.tld HTTP/1.1 200 303
May 30 09:15:30 2015 (2247) 127.0.0.1 - - GET
/3.0/lists/t...@domain.tld/held HTTP/1.1 200 90
May 30 09:15:31 2015 (2243) Uncaught runner exception: ('Connection
aborted.', ConnectionRefusedError(111, 'Connection refused'))
May 30 09:15:31 2015 (2243) Traceback (most recent call last):
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py,
line 544, in urlopen
body=body, headers=headers)
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py,
line 349, in _make_request
conn.request(method, url, **httplib_request_kw)
File /usr/local/lib/python3.4/http/client.py, line 1088, in request
self._send_request(method, url, body, headers)
File /usr/local/lib/python3.4/http/client.py, line 1126, in _send_request
self.endheaders(body)
File /usr/local/lib/python3.4/http/client.py, line 1084, in endheaders
self._send_output(message_body)
File /usr/local/lib/python3.4/http/client.py, line 922, in _send_output
self.send(msg)
File /usr/local/lib/python3.4/http/client.py, line 857, in send
self.connect()
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py,
line 155, in connect
conn = self._new_conn()
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py,
line 134, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py,
line 88, in create_connection
raise err
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py,
line 78, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/adapters.py,
line 370, in send
timeout=timeout
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py,
line 597, in urlopen
_stacktrace=sys.exc_info()[2])
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py,
line 245, in increment
raise six.reraise(type(error), error, _stacktrace)
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/packages/six.py,
line 309, in reraise
raise value.with_traceback(tb)
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py,
line 544, in urlopen
body=body, headers=headers)
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py,
line 349, in _make_request
conn.request(method, url, **httplib_request_kw)
File /usr/local/lib/python3.4/http/client.py, line 1088, in request
self._send_request(method, url, body, headers)
File /usr/local/lib/python3.4/http/client.py, line 1126, in _send_request
self.endheaders(body)
File /usr/local/lib/python3.4/http/client.py, line 1084, in endheaders
self._send_output(message_body)
File /usr/local/lib/python3.4/http/client.py, line 922, in _send_output
self.send(msg)
File /usr/local/lib/python3.4/http/client.py, line 857, in send
self.connect()
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py,
line 155, in connect
conn = self._new_conn()
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py,
line 134, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py,
line 88, in create_connection
raise err
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py,
line 78, in create_connection
sock.connect(sa)
requests.packages.urllib3.exceptions.ProtocolError: ('Connection
[Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf
Please help me to do this. if I put deployment/apache.conf into the virtualhost section of httpd.conf I got the following: httpd[30658]: AH00526: Syntax error on line 428 of /etc/httpd/conf/httpd.conf: httpd[30658]: WSGISocketPrefix cannot occur within VirtualHost section If I put them just outside of any virtualhost tags they produce Server error page. It would be great if I could put them into :443 virtualhost section to use SSL connection only for the list management/archives. Centos 7, Apache 2.4.6, last mailman-bundler. Danil ___ 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] right adding of mailman 3 conf lines to httpd.conf
Thank you Stephen! 2015-05-29 19:06 GMT+03:00 Stephen J. Turnbull step...@xemacs.org: Is deployment/apache.conf distributed by Mailman (presumably in Mailman-Bundler)? Have you changed it in *any* way (including anything that the installation instructions tell you do do)? No. AFAICS from the modwsgi docs, just move the WSGISocketPrefix out of apache.conf and into a non-vhost area of httpd.conf and you should be golden. It helps - I need to move these four directives outside of my virtualhost section: WSGISocketPrefix run/wsgi WSGIRestrictStdout On WSGIRestrictSignal Off WSGIPythonOptimize 1 to get working httpd.conf but I still can not access Mailman web interface. I tried https://domain.tld/ , https://domain.tld/mailman3 and both with :8000 port. Internal Server Error for the first couple, Not found for the second. Also there is nothing in the logs. If I open http://127.0.0.1:8000/mailman3 in `links` I got the error - see it in the attach. Danil ___ 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] Recipient address rejected: User unknown in virtual alias table
Now I have working Postorius and I can subscribe myself to the test list and get the welcome message (with incorrect urls in it!). But I could not post to the list or mail to the list owner from outside: 550 5.1.1 test-ow...@domain.tld: Recipient address rejected: User unknown in virtual alias table I've checked postfix/main.cf and everything looks right in it. Also I've ensured that var/data/*.db files are world-readable. Selinux is disabled. How could I debug this error? Thanks, Danil ___ 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] right adding of mailman 3 conf lines to httpd.conf
Also there is nothing in the logs. After I uncommented in httpd.conf the line ErrorLog /var/log/httpd/mailman-web_error.log I've got more info about the issue. It was permission error: ValueError: Unable to configure handler 'file': [Errno 13] Permission denied: '/var/log/mailman-web/mailman-web.log' After I corrected permissions for log file mentioned I can access Postorius and Hyperkitty. Everything looks working, I will test in more details later. Thanks! Danil ___ 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 3 and mysql
As I see on page https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html Mailman 3 should work with MySQL/MariaDB database. Could you please help me put right configuration to the [database] section of mailman.cfg file? Thanks. Danil ___ 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] help with ImportError: No module named 'psycopg2'
I'm still trying to get Mailman 3 ready for the production. I've set parameters for the production and trying to make post-update: --- (venv)[root@host mailman-bundler]# bin/mailman-post-update + '[' False == False ']' + mkdir -p /var/spool/mailman-web/static + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin collectstatic --clear --noinput --verbosity 0 + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin compress Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_link.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_removal.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/archival_options.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/unsubscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/login.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscription_requests.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscriptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_tasks.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/confirm_delete.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/summary.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_mailmansettings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/members.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_subscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_index.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/metrics.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_profile.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template
Re: [Mailman-Developers] help with ImportError: No module named 'psycopg2'
2015-05-27 22:57 GMT+03:00 Abhilash Raj raj.abhila...@gmail.com: There are actually 2 virtualenvs for mailman. One is the default one that you are working in, another one(venv-3.4) is probably automatically created by mailman-bundler as you can see in the logs above. This should fix your problem. $ source /usr/local/src/mailman-bundler/venv-3.4/bin/activate $ pip install psycopg2 $ (reactivate your original venv) Thanks Abhilash! It works! :) ___ 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 3.0 roadmap, feature-parity with mailman 2.x and documentation
2015-04-29 18:03 GMT+03:00 Brian Carpenter br...@emwd.com: Just to be clear, this is a stable fully working version of Mailman 3.0? I tried setting up Mailman 3 on a CentOS server about 2 weeks ago and had a number of issues including listinfo pages not working (404 errors), no clear directions on setting up users, various bugs such as internal server errors. The server admin that I had hired informed me there was a number of python related bugs and he felt Mailman 3 was not ready for production use. I am ready to give this another try but I want to make sure that this version will be a full working version of Mailman 3. I had similar experience a week ago (after PyCon sprint) and there were couple bugs in the installation process on Centos 7 including hard one with bad virtualenv version which is still not reflected in the installation manual: https://bugs.launchpad.net/mailman/+bug/1445764/comments/19 I suppose anyone who try to install Mailman on Centos 7 will face this bug. Danil ___ 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] web-interface for site owner for mm 2.1.x
2015-04-28 19:42 GMT+03:00 Mark Sapiro m...@msapiro.net: If you are asking if a site admin can remove a list via the web UI if the OWNERS_CAN_DELETE_THEIR_OWN_LISTS setting is the default No, the answer for MM 2.1 is no and there is no plan to change that. Personally I'm okay with the command line. But I have the client who asked me to install Mailman for her and intend to administer the installation by herself. She is not familiar with ssh/Linux console and uses cPanel-based hosting. Right now everything seems smooth for her besides lists removal - it can't be done without console access. Of course, we have workaround with OWNERS_CAN_DELETE_THEIR_OWN_LISTS setting, but in this case she cannot delegate list creation/administration to untrusted person. I understand the reasons why list removal is not available by default, but it would be great if we can somehow add special site owner permission to get her ability to remove lists (and to her only). (I'm asking about 2.1.x branch only, as I mentioned in the subject line.) Danil ___ 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] web-interface for site owner for mm 2.1.x
2015-04-28 19:17 GMT+03:00 Mark Sapiro m...@msapiro.net: If you set OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes in mm_cfg.py, every page in Mailman's admin GUI will have a Delete this mailing list (requires confirmation) link under Other Administrative Activities. Without this setting, the link is not there and attempts to remove a list via the http(s)://example.com/mailman/rmlist/LISTNAME CGI will fail. Hi everybody! How do you think, should site owner have an ability to remove lists from web interface also? We have separate password for list creation which can be set different from site owner password. We have special email alias mailman-ow...@domain.tld which belongs to whole installation admin. So we already have credentials for site owner to let him/her log in. Probably we also need full administration web interface for all mm_cfg.py amendments to avoid using console for the administration of Mailman installation at all. I wonder if nobody interested in this? Danil ___ 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] web-interface for site owner for mm 2.1.x
2015-04-28 20:39 GMT+03:00 Mark Sapiro m...@msapiro.net: cPanel provides a version of Mailman and has it's own list creation and deletion cPanel interface outside of the Mailman web UI. It seems if you used that, it would solve your problem. Nope. She has serious reasons to avoid using cPanel's Mailman. So it was disabled in favor of standard Mailman installation. I can give more details but webpanel talk is irrelevant to the topic of this discussion. Danil ___ 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 3 discussion
2015-04-21 0:34 GMT+03:00 Florian Fuchs f...@florianfuchs.com: OK, the problem was a file name conflict on the Python package index (due to an erroneously omitted pre-release suffix while parsing the version string of a previous beta-release), which eventually led to pypi delivering the previous release's tarball. I've associated a new file with the latest release on pypi so the correct tarball gets installed. Sorry for that... Okay, but what is workaround right now? I don't see any new revisions in the mailman-bundler... Danil ___ 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 3 discussion
2015-04-21 15:41 GMT+03:00 Florian Fuchs f...@florianfuchs.com: The change is not directly reflected in mailman-bundler. But running `buildout` again should install the newest version of mailman.client. Florian Now there is no response from http://127.0.0.1:8000/mailman3 at all... :( Just blank screen of links and 'Request sent' status. Danil ___ 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 3 discussion
2015-04-21 18:26 GMT+03:00 Aurelien Bompard aurel...@bompard.org: Make sure you started the runserver command again. Does it output something when you connect to the page? Yes I've checked it already - if it is not started I get 'Connection refused' error. If started, I get 'Received 0 B,...' or 'Request sent' in bottom status line and blank/black screen. update. Hm, somehow it returned to the working state. Domain has been successfully created. Thank you! Danil ___ 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 3 discussion
I would like to ask too. After successful fight with 'virtualenv' buggy version bug (https://bugs.launchpad.net/mailman/+bug/1445764) I've proceeded to initial setup through the Postorius web inteface. I opened the link http://127.0.0.1:8000/mailman3 in the 'links' browser and try to add new domain through 'Manage lists' - 'Domains' - 'Create domain' form. When I submit the form, I get the error: --- [root@host ~]# links http://127.0.0.1:8000/mailman3 TypeError at /mailman3/domains/new/ (p1 of 18) TypeError at /mailman3/domains/new/ create_domain() got an unexpected keyword argument 'owner' Request Method: POST Request URL:http://127.0.0.1:8000/mailman3/domains/new/ Django Version: 1.7.7 Exception Type: TypeError Exception Value:create_domain() got an unexpected keyword argument 'owner' Exception Location: /usr/local/src/mailman-bundler/eggs/postorius-1.0.0-py2.7.egg/postorius/models.py in create, line 117 Python Executable: /usr/local/src/venv/bin/python Python Version: 2.7.5 ['/usr/local/src/mailman-bundler/eggs/Django-1.7.7-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/postorius-1.0.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/HyperKitty-0.9.7-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/Whoosh-2.7.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/mock-1.0.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/djangorecipe-1.11-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/usr/local/src/venv/lib/python2.7/site-packages', '/usr/local/src/mailman-bundler/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/usr/local/src/mailman-bundler/eggs/lockfile-0.10.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_extensions-1.5.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_haystack-2.3.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/enum34-1.0.4-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/networkx-1.9.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/python_dateutil-1.5-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/mailmanclient-1.0.0b2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_browserid-0.11.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_compressor-1.5-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_paintstore-0.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/pytz-2015.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/robot_detection-0.3-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/cssmin-0.2.0-py2.7.egg', Python Path: '/usr/local/src/mailman-bundler/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/usr/local/src/mailman-bundler/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/djangorestframework-3.1.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/python_social_auth-0.2.7-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_gravatar2-1.3.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/six-1.9.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/decorator-3.4.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/httplib2-0.9.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/fancy_tag-0.2.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/requests-2.6.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_appconf-1.0.1-py2.7.egg', OK --- I wonder are there any way to connect to the Postorius through outer-accessible domain like http://mydomain.tld:8000/mailman3/ ? Danil 2015-04-20 17:51 GMT+03:00 Mark Sapiro m...@msapiro.net: On 04/20/2015 06:06 AM, Brian Carpenter wrote: I have a working installation of Mailman 3 on a CentOS 6 server. I have a number of questions regarding the use of it. Is this the right forum to ask those questions? Yes. We would also be interested in your feedback regarding the installation process. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ 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/danil%40smirnov.la 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] wrong path to python 3.4 while installing mailman 3
2015-04-18 3:52 GMT+03:00 Mark Sapiro m...@msapiro.net: Please see this wiki page http://wiki.list.org/x/17891734. It addresses Ubuntu, not CentOS, but talks about prerequisite things applicable to both although the apt-get package names may be different for Yum. This does not help. The error is the same. Filled a bug: https://bugs.launchpad.net/mailman/+bug/1445764 Danil ___ 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] wrong path to python 3.4 while installing mailman 3
And fixing the main problem with Python 3.4 path did not help to make buildout command successful. I've posted the error message as a comment of my bug report: https://bugs.launchpad.net/mailman/+bug/1445764 2015-04-18 15:21 GMT+03:00 Danil Smirnov da...@smirnov.la: 2015-04-18 3:52 GMT+03:00 Mark Sapiro m...@msapiro.net: Please see this wiki page http://wiki.list.org/x/17891734. It addresses Ubuntu, not CentOS, but talks about prerequisite things applicable to both although the apt-get package names may be different for Yum. This does not help. The error is the same. Filled a bug: https://bugs.launchpad.net/mailman/+bug/1445764 Danil ___ 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] wrong path to python 3.4 while installing mailman 3
Tried export PATH=/usr/local/bin:$PATH, does not help - the error is same: Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpePyrQ3/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: Нет такого файла или каталога While: Installing mailman. 2015-04-17 21:00 GMT+03:00 Pranjal Yadav godricg...@gmail.com: Add the following to your ~/.bashrc file: export PATH=/usr/local/bin:$PATH Alternatively, you can simply rename /usr/bin/python to /usr/bin/python3.4 and create a symlink pointing to the new version, e.g. ln -s /usr/local/bin/python /usr/bin/python On Fri, Apr 17, 2015 at 11:24 PM, Danil Smirnov da...@smirnov.la wrote: But [root@host ~]# which python3.4 /usr/local/bin/python3.4 2015-04-17 20:38 GMT+03:00 Danil Smirnov da...@smirnov.la: Have you meant [root@host ~]# which python3 /usr/bin/which: no python3 in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) ? 2015-04-17 19:59 GMT+03:00 Pranjal Yadav godricg...@gmail.com: Can you check with where python3 and post the output. On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov da...@smirnov.la wrote: I'm trying to install Mailman 3 using this manual: http://mailman-bundler.readthedocs.org/en/latest/ After step (venv)[root@host src]# pip install zc.buildout (venv)[root@host src]# buildout I've got an error Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpuGe9kP/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not found While: Installing mailman. I have Python 3.4. in /usr/local/bin directory, not /usr/bin. Please help. Danil ___ 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/godricglow%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- *Pranjal Yadav* *IIT Kharagpur* ___ 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/godricglow%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- Pranjal Yadav IIT Kharagpur ___ 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] wrong path to python 3.4 while installing mailman 3
But [root@host ~]# which python3.4 /usr/local/bin/python3.4 2015-04-17 20:38 GMT+03:00 Danil Smirnov da...@smirnov.la: Have you meant [root@host ~]# which python3 /usr/bin/which: no python3 in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) ? 2015-04-17 19:59 GMT+03:00 Pranjal Yadav godricg...@gmail.com: Can you check with where python3 and post the output. On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov da...@smirnov.la wrote: I'm trying to install Mailman 3 using this manual: http://mailman-bundler.readthedocs.org/en/latest/ After step (venv)[root@host src]# pip install zc.buildout (venv)[root@host src]# buildout I've got an error Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpuGe9kP/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not found While: Installing mailman. I have Python 3.4. in /usr/local/bin directory, not /usr/bin. Please help. Danil ___ 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/godricglow%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- *Pranjal Yadav* *IIT Kharagpur* ___ 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] wrong path to python 3.4 while installing mailman 3
Have you meant [root@host ~]# which python3 /usr/bin/which: no python3 in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) ? 2015-04-17 19:59 GMT+03:00 Pranjal Yadav godricg...@gmail.com: Can you check with where python3 and post the output. On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov da...@smirnov.la wrote: I'm trying to install Mailman 3 using this manual: http://mailman-bundler.readthedocs.org/en/latest/ After step (venv)[root@host src]# pip install zc.buildout (venv)[root@host src]# buildout I've got an error Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpuGe9kP/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not found While: Installing mailman. I have Python 3.4. in /usr/local/bin directory, not /usr/bin. Please help. Danil ___ 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/godricglow%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- *Pranjal Yadav* *IIT Kharagpur* ___ 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] wrong path to python 3.4 while installing mailman 3
Are you absolutely sure about renaming? As I understand I need both Python 2.7 which is /usr/bin/python and 3.4 which is /usr/local/bin/python3.4 for the Mailman installation. 2015-04-17 21:00 GMT+03:00 Pranjal Yadav godricg...@gmail.com: Add the following to your ~/.bashrc file: export PATH=/usr/local/bin:$PATH Alternatively, you can simply rename /usr/bin/python to /usr/bin/python3.4 and create a symlink pointing to the new version, e.g. ln -s /usr/local/bin/python /usr/bin/python On Fri, Apr 17, 2015 at 11:24 PM, Danil Smirnov da...@smirnov.la wrote: But [root@host ~]# which python3.4 /usr/local/bin/python3.4 2015-04-17 20:38 GMT+03:00 Danil Smirnov da...@smirnov.la: Have you meant [root@host ~]# which python3 /usr/bin/which: no python3 in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) ? 2015-04-17 19:59 GMT+03:00 Pranjal Yadav godricg...@gmail.com: Can you check with where python3 and post the output. On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov da...@smirnov.la wrote: I'm trying to install Mailman 3 using this manual: http://mailman-bundler.readthedocs.org/en/latest/ After step (venv)[root@host src]# pip install zc.buildout (venv)[root@host src]# buildout I've got an error Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpuGe9kP/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not found While: Installing mailman. I have Python 3.4. in /usr/local/bin directory, not /usr/bin. Please help. Danil ___ 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/godricglow%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- *Pranjal Yadav* *IIT Kharagpur* ___ 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/godricglow%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -- *Pranjal Yadav* *IIT Kharagpur* ___ 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] wrong path to python 3.4 while installing mailman 3
2015-04-17 21:18 GMT+03:00 Mark Sapiro m...@msapiro.net: You only need ln -s /usr/local/bin/python3.4 /usr/local/bin/python3 You don't need to rename anything. Thanks Mark! I did this: # ls -l /usr/local/bin/ итого 68 -rwxr-xr-x 1 root root 101 apr 17 18:28 2to3-3.4 -rwxr-xr-x 1 root root 241 apr 17 18:28 easy_install-3.4 -rwxr-xr-x 1 root root99 apr 17 18:28 idle3.4 -rwxr-xr-x 1 root root 213 apr 17 18:28 pip3.4 -rwxr-xr-x 1 root root84 apr 17 18:28 pydoc3.4 lrwxrwxrwx 1 root root24 apr 17 21:19 python3 - /usr/local/bin/python3.4 -rwxr-xr-x 2 root root 17544 apr 17 18:28 python3.4 -rwxr-xr-x 2 root root 17544 apr 17 18:28 python3.4m -rwxr-xr-x 1 root root 3030 apr 17 18:28 python3.4m-config -rwxr-xr-x 1 root root 236 apr 17 18:28 pyvenv-3.4 But I've got the same error again: Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmplM1FLA/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: Нет такого файла или каталога While: Installing mailman. I wonder don't I need to do ln -s /usr/local/bin/python3.4 /usr/bin/python3.4 as the error says? Danil ___ 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] wrong path to python 3.4 while installing mailman 3
I'm trying to install Mailman 3 using this manual: http://mailman-bundler.readthedocs.org/en/latest/ After step (venv)[root@host src]# pip install zc.buildout (venv)[root@host src]# buildout I've got an error Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpuGe9kP/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not found While: Installing mailman. I have Python 3.4. in /usr/local/bin directory, not /usr/bin. Please help. Danil ___ 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] wrong path to python 3.4 while installing mailman 3
2015-04-17 21:24 GMT+03:00 Danil Smirnov da...@smirnov.la:
I wonder don't I need to do
ln -s /usr/local/bin/python3.4 /usr/bin/python3.4
as the error says?
I've created this symlink and that's what I've got now:
(venv)[root@host mailman-bundler]# ln -s /usr/local/bin/python3.4
/usr/bin/python3.4
(venv)[root@host mailman-bundler]# buildout
Develop: '/usr/local/src/mailman-bundler/.'
warning: no files found matching '*.in' under directory 'mailman_bundler'
warning: no files found matching '*.in' under directory 'deployment'
warning: no files found matching 'deployment/mailman-web.logrotate.conf'
Updating mailman-web.
Updating main.
Installing mailman.
Running virtualenv with interpreter /usr/bin/python3.4
Using base prefix '/usr/local'
New python executable in /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4
Also creating executable in /usr/local/src/mailman-bundler/venv-3.4/bin/python
Failed to import the site module
Traceback (most recent call last):
File /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site.py,
line 67, in module
import os
File /usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/os.py,
line 616, in module
from _collections_abc import MutableMapping
ImportError: No module named '_collections_abc'
ERROR: The executable
/usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 is not
functioning
ERROR: It thinks sys.prefix is '/usr/local/src/mailman-bundler'
(should be '/usr/local/src/mailman-bundler/venv-3.4')
ERROR: virtualenv is not compatible with this system or executable
/tmp/tmpTl6JgC/run: line 2:
/usr/local/src/mailman-bundler/venv-3.4/bin/pip: Нет такого файла или
каталога
While:
Installing mailman.
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File
/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py,
line 1946, in main
getattr(buildout, command)(args)
File
/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py,
line 626, in install
installed_files = self[part]._call(recipe.install)
File
/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py,
line 1370, in _call
return f()
File
/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py,
line 56, in install
self.execute()
File
/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py,
line 69, in execute
run_commands(cmds, self.shell)
File
/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py,
line 39, in run_commands
check_call('%s %s' % (shell, tmpfile), shell=True)
File /usr/lib64/python2.7/subprocess.py, line 542, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'sh /tmp/tmpTl6JgC/run' returned non-zero
exit status 127
Danil
___
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] wrong path to python 3.4 while installing mailman 3
2015-04-17 22:00 GMT+03:00 Mark Sapiro m...@msapiro.net: pull' and remove the venv and venv-3.4 directories), and follow the README.rst in the latest rev. I've checked the file and found that it offers the same installation instructions before my error stop than http://mailman-bundler.readthedocs.org/en/latest/ D. ___ 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] wrong path to python 3.4 while installing mailman 3
2015-04-17 22:00 GMT+03:00 Mark Sapiro m...@msapiro.net: At this point, I suspect you haven't activated the venv that you had active when you started. (Every time you start a new shell, you have to activate the venv for that shell.) I am still on the same shell that when I started. My prompt looks like: (venv)[root@host mailman-bundler]# I suggest you remove your mailman-bundler branch and get the latest with 'bzr branch lp:mailman-bundler' I've got this branch TODAY so I think it's latest. So, does it mean that there is no way to install Mailman 3 using manual mentioned? Danil ___ 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
