As a Debian fanboy and also a mailman addict, I'd like to try packaging it
in Debian. As I'm not a DD and as I'm not in a hurry, I'd like to take some
time to think about what would be relevant.
For that, I'd like to have some help. And I was suggested to come here and
I decided to use https://gitlab.com/groups/mailman as a basis for my work.
First of all, to create the source package, I've to think about what to put
It seems that if I want to have a good source package, I need 5 repos :
- HyperKitty - MailMan Plugin
My first question is "Am I right?". And the second one is whould I consider
looking into mailman-suite-doc and also have it in the source package?
On another way, I also see that there is a standalone postorius repo and
also some django project files for HyperKitty in another one. I have the
impression it is more designed for people to work on as standalone -
forkable projects for other features, and so I wouldn't need them in a
Am I also right?
Thanks for your answer, I hope I'll be able to make this package look as
you'd like. :)
Hi Cabal. I'm sorry that I've neglected Mailman so much for the past
several months; I've just registered for PyCon 2016 and will be
ramping up my participation especially leading up to that.
has just announced that it wants to "identify up to 10 projects we
rely on and can fund in a thoughtful, meaningful way by December
12th". They use Mailman and if we can identify useful ways they can
spend that money to advance Mailman's development and usefulness to
them (e.g., paying for someone's time to get packaging or localization
to a better state), I'd be happy to take point on organizing that
Again, regrets on my absence.
(I hope I'm not off topic..)
Since I maintain a couple of dozen lists, I need a way to reduce the
time taken to process them. I use listadmin, a command line tool to
manipulate the queues of messages held for moderator approval and
It's a great tool that saved me a lot of time.
But, sadly, the upstream author does not work anymore on the listadmin
script since years.
So, new versions of mailman brings new bugs, and make it less and less
It's not a big script, but I haven't the technical skills to maintain
I was hoping that someone on this list, with the inside knowledge of
mailman, could maintain it, or write something similar.
It would save me (and others) so much time !
Thank you for your work on mailman,
and others unreported..
Take a look at these:
These add new headers based on DKIM that document a chain of custody
for mail. It would let mail providers accept list mail that DMARC
would otherwise reject. The drafts are a mess (the XML versions are
easier to read than the txt), but I think the design is sound. They
are intended to be implemented via upgraded DKIM libraries, and the
idea is to allow lists to work like they always have, without any
changes visible to users. You can intuit from the authors who's
likely to implement it.
It'd be helpful for people to look at it and write to the contact
address in the first draft and tell them how likely it is that Mailman
would support it, or what problems it would present.
> Installing mailman-web.
> Error: There is a version conflict.
> We already have: pbr 1.8.1
> but lockfile 0.11.0 requires 'pbr!=0.7,<1.0,>=0.6'.
It looks like lockfile does not actually need a specific version of pbr.
not sure though since I manually installed mailman
I have looked in several list archives for different approaches for Mailman 3 installation, and am trying a few things. I have got a new Debian 8.2 install, and installed the Python 2 and 3 developer tools etc.
I am making a virtual environment in /opt/mailman.
When running buildout, I get up until this point:
Getting distribution for 'djangorestframework>=3.0.0'.
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
Got djangorestframework 3.2.4.
Getting distribution for 'django-gravatar2>=1.0.6'.
zip_safe flag not set; analyzing archive contents...
Got django-gravatar2 1.3.0.
Error: There is a version conflict.
We already have: pbr 1.8.1
but lockfile 0.11.0 requires 'pbr!=0.7,<1.0,>=0.6'.
Any ideas as to how to resolve?
On 10/08/2015 11:40 PM, Aswin kumar wrote:
> I am new to python programming language and I saw that there are two
> versions python2 and python3. Which one should I start learning ? Should I
> learn python2 first and then switch to python 3? I am asking this question
> here as maiman3 has switched to python3 , but some other projects still
> stick to python2, so I am kind of confused which version to start with.
Definitely start with Python 3.
There is still much legacy Python 2 code, and many projects have a hard
time porting to Python 3 because of dependencies on other packages which
are still Python 2, but the future is Python 3, and any new code is best
as Python 3.
The only reason to learn Python 2 at this point is if you are tasked
with supporting a legacy Python 2 project.
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
I am new to python programming language and I saw that there are two
versions python2 and python3. Which one should I start learning ? Should I
learn python2 first and then switch to python 3? I am asking this question
here as maiman3 has switched to python3 , but some other projects still
stick to python2, so I am kind of confused which version to start with.
I've hacked per-post AES encryption of subscriber addresses into
Decorate.py so that I have a subscriber address identifier available for
situations where subscribers have lost redirections in force and can't
get headers to me.
Everything works, and I can use the substitution %(user_skey)s in the
footer, but I get a nasty warning on the Non-digest options page,
"Warning: The following illegal substitution variables were found in the
msg_footer string: user_skey".
Where in the code can I list this substitution variable so that it
doesn't throw this error on this page?
Lindsay Haisley | "The only unchanging certainty
FMP Computer Services | is the certainty of change"
http://www.fmp.com | - Ancient wisdom, all cultures
Mark Sapiro helped me with some basic config issues earlier but now i'm
stuck here; my web browser shows me:
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later."
my server's apache postorius error log shows me:
[Tue Oct 06 15:52:34.961249 2015] [:error] [pid 11691] (13)Permission
denied: [client <IP>:42590] mod_wsgi (pid=11691): Unable to connect to
WSGI daemon process 'hyperkitty' on '/run/httpd/wsgi.11685.0.1.sock'
after multiple attempts.
this occurs when i try to access:
if i try /postorius/, i see same browser result and similar apache log
[Tue Oct 06 15:58:53.355159 2015] [:error] [pid 11693] (13)Permission
denied: [client <IP>:42654] mod_wsgi (pid=11693): Unable to connect to
WSGI daemon process 'postorius' on '/run/httpd/wsgi.11685.0.2.sock'
after multiple attempts.
MM3 components installed from hyperkitty-el.repo and using apache 2.4.6
on centos 7. python 2.7 and 3.4 installed.
What's missing here? Thanks all.
- Fabe S.