Hi people,
I'm working on HyperKitty, and I've understood that I need to add this
section to mailman.cfg to enable it :
[archiver.hyperkitty]
class: hyperkitty.lib.archiver.Archiver
enable: yes
base_url: http://hyperkitty.example.com
That works well. However, I need another key to
Why do you think that the configuration of HK should be a part of the MM core?
I didn't intend to put all of HK's config in mailman.cfg of course.
But I'm supposed to reference a class in the archiver.hyperkitty
section, which will be imported on startup, so it must be on the same
host.
Since
Sorry I messed up with a list-reply, so you people missed Richard's reply.
What concerns me is that MM core should not depend on Django in order to run.
The Archive interface needs to accept the message and place it in the store.
MM won't depend on Django, only if the HK section in mailman.cfg
You had mentioned a reference to the Django settings for HK.
Yes, my idea was to have something like that in the mailman.cfg file :
[archiver.hyperkitty]
enabled: yes
class: hyperkitty.archiver.Archiver
base_url: http://archives.example.com
conf_file: /path/to/django/app/settings.py
Yeah, sorry I'm not familiar enough with HyperKitty to know how you get
messages *into* it. ;)
Don't be sorry for not knowing *everything* ;-)
Aurélien
___
Mailman-Developers mailing list
Mailman-Developers@python.org
Hi Mailmaners,
Here's a version of the external configuration files patch. As Barry
suggested, it adds a configure entry in the archiver's section,
which can point to an ini-compatible configuration file (ConfigParser
is used) for additional archiver-specific configuration.
I've migrated the
Is there any chance you could push this to Launchpad as a branch?
Sure. I've pushed it to Launchpad and filed a merge proposal.
Cheers,
Aurélien
___
Mailman-Developers mailing list
Mailman-Developers@python.org
Hello Mailmaners,
The HyperKitty project was historically using Bazaar as it VCS, and
was hosted on fedorahosted.org. An essential component was split off
(KittyStore), which was initially source-controlled with Git and
hosted on Github.
I'm trying to bring back some coherence into this, and
So, if I understand correctly, Storm add to its exception the error
message it gets from PostgreSQL, which is a bytestream (encoded in
UTF-8 on your system). But Mailman sends its logs to the logger as
unicode, thus the exception must be converted to unicode, and that's
where the
Hey there!
I have a question about emails generated by Mailman3. This is an
example of a message held notification (your message awaits
moderator approval). According to the template, Mailman inserts a
cancel link at the end of the email:
If you would like to cancel this posting, please visit
OK, thanks for the explanation Barry
A.
___
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:
Hey!
I'd like to discuss what happens when an email is sent by both a
member and a nonmember in Mailman3. How is that possible? Very easy,
here's my use case : I have my own domain, say example.com, and for
convenience and portability I choose to use Gmail as a
server/storage/interface. My main
it on my setup, it works as expected.
Aurélien
2014-03-12 1:43 GMT-03:00 Stephen J. Turnbull step...@xemacs.org:
Aurelien Bompard writes:
I'd like to discuss what happens when an email is sent by both a
member and a nonmember in Mailman3. How is that possible? Very easy,
here's my use case
Hey!
On Mailman3, every message held notification has XXX as the
reason. This comes from the HoldChain class in mailman/chains/hold.py,
where XXX is hardcoded.
I'd like to fix that. I think there could be a list in the message
metadata to which each matching rule would add a short description of
Hey people,
I'm trying to create a User in Mailman 3 from an existing Address. If
I were using the Python interface, that would be very easy: just
create the user with no address and then link the existing address to
it.
However, I'm using the REST interface. In
So the address is currently unlinked? And you don't want to link it to an
existing user, but to a new user you're about to create?
Exactly. The address is unlinked and unverified. I'd like to create a
user for it.
Sketching out an approach:
[...]
Interesting. I'll look into that at some
Can you open a bug?
Done: https://bugs.launchpad.net/mailman/+bug/1312884 :-)
A.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Hey Abhilash!
I was trying out mailman-bundler and have setup a demo here [1]. I notice
that with 'USE_SSL=True' in development.py deployment settings, there is a
redirect loop while logging in[2]. I had to disable it to deploy.
Hmm, this parameter should be ignored if DEBUG is True. But
While I was trying to deploy using nginx and
uwsgi/gunicorn I found that they expect the script to have .py extension
and not .wsgi. All new django versions currently create a wsgi.py file along
with the project itself. So I was thinking we should change that in our code
too.
OK, this file
OK, fixed and pushed. I've added instructions for running via Gunicorn
in the README, can you check them?
Thanks!
Aurélien
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Currently there is no links to migrate between postorius(the mailman3 web
ui) and hyperkitty(the archiver).
Yeah, and that's something I'll fix as soon as I'm done squashing the
main bugs I have in my pile.
Aurélien
___
Mailman-Developers mailing
Hey y'all,
In Mailman 3, I'm trying to create a list that would require its
moderators to approve subscriptions. In the Mailman doc, this is
commonly referred to as a closed list. However, I can't find a way
to create such a list, nor the database field which would mark it as
such.
I've also seen
For your information, I have written a small SELinux module for Mailman3,
it's included in my Fedora RPM and works fine. In the future (when MM3 is
out), I'll ask for integration in the core policy.
Aurélien
___
Mailman-Developers mailing list
Got hit by that too, I just created a merge request with the missing file :
https://code.launchpad.net/~abompard/mailman/pgsql_upgrade/+merge/227289
Could anyone have a quick look at this?
Aurélien
___
Mailman-Developers mailing list
Hey Tobias,
Sorry for not replying to your email but I did read it.
having a two digit month in the URL would bring it closer to the ISO 8601
format.
Using leading zeros in URLs is something I had already noticed and wanted
to do, but I guess I never wrote it down when I thought about it and
Hey folks,
Mailman stores user_ids as UUIDs in the database, and they are converted on
the fly to integers by the REST API.
However, the mailmanclient library do not convert them back to UUID. Do you
think this is something that it should do, or should I handle this
conversion in my own code?
Hi Florian!
I think mailmanclient should not expose a different value as the REST
API does (the fact that it's an int representation of a uuid isn't
exactly obvious from the outside, so a non-explicit conversion could
potentially lead to some confusion).
Hmm, to me the current situation is
If the user_id value changes depending on whether
you are using the API directly via HTTP or through mailmanclient, that
might be hard to understand.
Ah, very good point. I'll do the conversion myself then I guess.
A.
___
Mailman-Developers mailing
So Aurelien and Florian, what do you think? Should we use the hex
representation of the UUID and should I keep backward compatibility.
If we can't see any valid reason for converting to ints today, I would
personally vote for not converting in the REST API, and for mailman.client
to return
Hey Guillaume,
The new SQLAlchemy backend has just been merged as you've probably seen. It
should upgread seamlessly from the previous Storm backend, but nothing has
been done to make transition from SQLite to PostgreSQL possible.
If I were you I would take the following steps:
1. upgrade to the
Hey!
Indeed I'm the HyperKitty dev, and I wrote mailman-bundler too. Sorry I
couldn't reply earlier.
Yes it reloaded to '/archives/' correctly. But the new page seems
NOT logged in. The Login button is still there, and the
administrative options don't appear.
Please check your webserver
Very cool, I'll have a look!
A.
___
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:
Hi *,
I'd like to discuss the algorithm we use to enforce a list's default
moderation action. Here's what I understand:
- the list's default_moderation_action setting is stored in the database
and can be changed via the REST interface
- when a new member is created, its moderation_action is
Hi * !
I'm trying to fix bug 1060951 (that I reported), and no matter how I poke
at it, I can't find the proper way to solve it, so I'd like to share my
thoughts with you.
https://bugs.launchpad.net/mailman/+bug/1060951
The issue is with our unicode-enabled subclass of Python's
Thanks to you all !
I've looked, again briefly because after a short time my head spun out
of control, at trying to fix it by overriding additional methods like
_get_params_preserve(), but I didn't get far.
Yeah, I tried that too, not much more luck...
To be honest,
Hmm, that was easier than I thought :
https://code.launchpad.net/~abompard/mailman/bug-1060951/+merge/243401
All tests pass, and no unicode warning from SQLAlchemy in the tests.
A.
2014-12-02 11:42 GMT+01:00 Barry Warsaw ba...@list.org:
On Dec 02, 2014, at 11:26 AM, Aurelien Bompard wrote
At first I thought I had introduced a regression but it's actually just
my name :-)
Don't blame me, I didn't choose it!
(Florian, can you fix that? And by the way my last name is Bompard,
without the A)
Thanks !
A.
2014-12-11 21:08 GMT+01:00 Andrew Stuart andrew.stu...@supercoders.com.au:
One of my top priorities has been to port Mailman 3 (core) to Python 3.
This
work is now complete, and ready to be merged into trunk. No doubt bugs
still
lurk, but at least the entire test suite is passing.
Congrats !
* A few database columns have changed from LargeBinary to Unicode. I
I'm having some trouble with this because the system alembic doesn't have
access to the mailman source tree, which it needs (you get import
errors). I
tried to run alembic out of the .tox virtualenv, but that fails because the
mailman config system needs to be initialized.
Right, I'm
But there could be! I took a very quick look at HK (but not KittyStore)
and
it doesn't look like you need much. What if I added a REST API to access
the
core's system configuration settings?
That would work.
Yep, I missed that. Is it possible to feed HK messages out-of-process?
E.g.
This was a design mistake, I think.
Yeah, I see that now. But at that time, if I had known that I had two more
years (and counting) before MM3 was released, I'd probably have made
different choices.
I hope I'm not making the same mistake again.
As I mentioned, I think LMTP *could* work, but
I must also consider how much work it would be to just port HyperKitty
KittyStore to Python3.
All things considered, it may very well be faster and more reliable.
A.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
What if a site wanted to run them on different VMs for example?
Yeah, but certainly there should be a limit to that. What if a site wanted
to run each mailman runner on a different VM for example?
Oh well, I guess there's no other way. I hope it's not going to be a mess
to configure, I'd like
Hey people,
I am pleased to announce that the Mailman bundler tool is working again.
If you want to easily install Mailman + HyperKitty + Postorius, just follow
this tutorial:
http://mailman-bundler.readthedocs.org
It is not very suitable for development though, because I get the code from
the
Do you think I can help you work on that? Or would you prefer doing the
initial branch resurrection?
Anything I need to know before I start?
Alright, I resurrected your branch to the best of my understanding. I hope
it's more Lazarus than Reanimator.
Have a look at the workflow illustrated in my crappy Dia file, which I
think is an accurate
representation of how the policy should work.
Hmm, could you point me to this Dia file please, I can't find it. Thanks!
Aurélien
___
Mailman-Developers
Aurélien Bompard - Postorius
Actually I'm working on HyperKitty.
Thanks for the pic !
A.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ:
I'm interested in contributing to the Hyperkitty archiver. Specifically,
it looks like some requested features for Hyperkitty include rss syndication
for entire mailing lists/specific users/specific threads, and the ability
to view entire threads as plaintext and download that plaintext.
We
Would you mind if I used the Hyperkitty POST code as the basis for an example
POST archiver for Mailman?
Sure, no problem.
Aurélien
___
Mailman-Developers mailing list
Mailman-Developers@python.org
Hey David, here are my thoughs on the challenges:
1) Determine which messages to include in the mbox.
An entire list archive is clearly one choice, but is there also
interest in generating mbox files for specific threads, list archieves
between specific dates, etc.?
Hmm, depending on the
In my proposal I suggested using any of several asynchronous job queue
libraries, such as Celery or Huey. These all use redis as a back-end.
Because I have no experience with asynchronous job queues, I'm not sure if
this is too much baggage for our purposes. Maybe we just don't want the
extra
Oops. Looks like I'd forgotten to push them. They should now be
available in
lp:~barry/mailman/subpolicy
Got it.
OK, the SubscriptionWorkflow seems correct in implementation but it has
almost no tests, so I'll write some.
But there's something else: the SubscriptionWorkflow class does not
Nope. It needs to be hooked up. The branch wasn't merged because it was
incomplete.
Oh, and the _send_confirmation method is also not implemented. Could
you briefly explain how does the confirmation system work? (or point
me to the doc, I didn't find it)
Thanks
Aurélien
Nope. It needs to be hooked up. The branch wasn't merged because it was
incomplete.
Ah alright, I'm just adding some tests but it would probably be better you
did the hooking up... (or I'll need a good amount of guidance)
Thanks
Aurélien
___
As for the `password` key: It's recognized by mailman.client and
exposed within the mlist instance's `requests` property. But it's used
nowhere in postorius and I would be surprised if it's used anywhere in
hyperkitty (Aurélien...?). I guess it can go away.
No problem, I don't use pending
Aurelien I’d be interested to hear your thoughts on this topic.
Well, the implementation of the archiver for HyperKitty does POST to
archive emails :
https://github.com/hyperkitty/mailman-hyperkitty/blob/master/mailman_hyperkitty/__init__.py
However, there are a few things specific to
We are (as in Patrick is) currently working on getting a Fedora 22 builder
added
to the jenkins instance so that we have a python 3.4 available for you folks
if
you so desire :)
Fedora 21 has Python 3.4, so that would be enough.
A.
___
Now there is no response from http://127.0.0.1:8000/mailman3
at all... :(
Just blank screen of links and 'Request sent' status.
Make sure you started the runserver command again. Does it output
something when you connect to the page?
A.
___
Hello, and thanks for your report.
When i try to signup via hyperkitty i get:
Using the internal auth/registration system isn't really tested
supported, it's better to use the Persona button. However, that's a
real bug and I just pushed a commit to fix it:
So the current python-social-auth is not buildout compatible?
It seems so, yeah. I did not investigate further to see what buildout
was choking on.
Is it my turn to file a bug in the python-social-auth bug tracker?
That would be great! Thanks
Aurélien
Hey!
No eggs found in
/tmp/easy_install-LK6bYy/python-social-auth-0.2.9/egg-dist-tmp-FzLeGP (setup
script problem?)
I'm getting the same error, this does not look like a problem in the
bundler but rather in the latest version of python-social-auth. It
works if you insert
Logging in via Email is probably broken in the Mailman 3.0 release.
AFAIR it has been fixed the main trunk. We suggest people to use the
Persona Login instead of the email.
I fixed it in HyperKitty and released a new tarballs a few days later,
it should be OK but it's not officially supported
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
It is surprising, however, that the
buildout just doesn't do the install itself. Restarted the build
and...
It should but there's a bug in the latest version of
python-social-auth that prevents the automatic install:
https://github.com/omab/python-social-auth/issues/623
For the time being,
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.
Ah, right, the fact
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py,
line 101, in list_url
return self._get_url({mlist: mlist.fqdn_listname})
File
/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py,
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.
Actually merging two existing users is indeed a tricky thing because users
link to so many other interesting bits and pieces. Two separate users have
two separate memberships, linked addresses, preferred addresses, and yes,
preferences. There are also the created_on, display_name, and (the
Hey devs!
I'm hitting a problem when migrating from 2.1 to 3, but I think it's a
generic issue (or rather a missing feature) and I'd like to fix it.
If I try to associate an existing address to an existing user (without
this address obviously), the Mailman API will reply with a 400 error
User
Hey all!
I'm hitting another issue in my migration from 2.1 to 3.x. In 2.1,
there was an option called "header_filter_rules" used mainly for spam
control, and advertised as such in the CGIs. These rules contained a
regex and an action to take on a match : defer, approve, reject,
discard,
> It's probably going to require a separate table foreign
> keyed to the mailing list which contain a list of regexps and their actions,
Yeah, it's currently a python list pickled into the header_matches
field of a mailinglist, we can do better :-)
> Then this has to be exposed through the REST
> You're right that model classes should never be imported outside mailman/model
> although there are a few violations of this rule. It's less hard-and-fast for
> tests since sometimes that's just the most convenient way to handle it.
> [...]
Great explanation, thanks.
I'll send a merge request
OK, I have something that follows these requirements (except the
site-defaults + site-config thing, currently site-wide checks take
precedence).
If you want to look at it :
https://gitlab.com/abompard/mailman/commits/import-header-matches
If you have some time Barry, I'd like your review on some
Hey Fabian,
> Does anyone know where I can find more info on deploying mailman 3 on centos
> 7 aside from the standard docs site?
I'm currently packaging Mailman3 and HyperKitty + Postorius for Red
Hat / CentOS 7. My packages are here:
Hey people,
Mailman has the notion of "verified" email addresses. When a user is
created / registered in Postorius, a Mailman user can be created. It's off
by default but it seems like a logical thing to do.
This user will be created when the client visits the user profile or
preferences pages
Hi folks!
As you probably know, Mozilla Persona is going away very soon, and we had
plans to migrate our web authentication to the django-allauth library so we
could support local accounts properly. These last weeks I've been working
on that and my work is almost complete.
I've done some
Here are the branches, so you don't have to go hunt for them:
- django-mailman3: https://gitlab.com/mailman/django-mailman3/tree/allauth
- hyperkitty: https://gitlab.com/mailman/hyperkitty/tree/allauth
- postorius: https://gitlab.com/abompard/postorius/tree/allauth
A.
Hey people!
We now have enough lists and activity that Mailman's REST API is
becoming a bottleneck, since it only answers one request at a time.
Is there a way to start mutiple REST runners? Or to make the REST
runner multithreaded?
Thanks!
Aurélien
Hey folks!
I thought I'd keep you posted on a rather big change that landed in
HyperKitty a couple weeks ago. It will be useful for those of you who
run the master branch. If you updated and HyperKitty started requiring
Redis or not updating some parts of the UI, that may be the reason.
I have
> Could you open an issue on Core for this?
There you go: https://gitlab.com/mailman/mailman/issues/327
> Have you done any other analysis on where the bottlenecks are? Is it CPU, db,
> I/O?
I haven't investigated properly but it seems to be the database (which
is on another host).
>
Hey! :-)
I hope you're having a great time at PyCon :-)
#104 - Server Error (500) upon login with duplicate email addresses
> (we're thinking maybe just turning that into a non-500 error?)
>
Not sure I can do much to prevent it, it doesn't seem to go through my code
at all. And since it's a
>
> One thing that I wanted to announce before I start is breaking up
> mailmanclient
> from one giant module (src/mailmanclient/_client.py) to seperate class
> based
> modules.
Yes please, I've been putting that off for a long time but I think it's
needed too.
A.
>
> > As I understand, AcceptableAliases are defined as regular expressions,
> > what if Mailman put the values that are a valid list name to
> > transport_maps? Converting regex to a listname doesn't sound like a
> > straight forward thing to me though.
>
> I think that's going to be too complex
Hey folks!
I wanted to rename a list (only the list_name, not the list_id) and I
figured I would make the transition smoother by adding an "AcceptableAlias"
with the old name. I did that and realized that the acceptable aliases are
not added to the postfix_lmtp file, as a result emails sent to
84 matches
Mail list logo
