On 05/12/2018 02:13 AM, Eric Abrahamsen wrote:
I've got mailman3 up on Ubuntu 16.04, in a virtualenv, and (eventually) got everything working mostly okay.
My last hurdle is archiving into hyperkitty: the web interface says "no archived list yet".
The list I'm starting with is set to archive both to prototype (which I set up in the beginning, before I got hyperkitty going) and to hyperkitty. There appear to be no further boxes I can check, and mailman_hyperkitty.cfg is in place and I think correct.
I think it's nearly working because new messages get filed to ./var/archives/hyperkitty/spool, in individual *.pck files, but then these files don't go anywhere, and the archives don't appear in the web view.
It could be a problem with cronjobs, with qrunner, or maybe there's just one last hidden switch in a database somewhere that I haven't thrown. But I can't find anything.
Any hints? My best guess is that it's a config issue. The backend should log something about the archives. can you share that with us? Thanks for the nudge -- I was looking in the wrong logs. That got me all
On 05/12/18 16:29 PM, Simon Hanna wrote: the way to seeing that my base_url is wrong: it's currently http://localhost/hyperkitty, because that's the default in the sample config, but I don't know what it should be. The docs say localhost is good, but I don't actually know where it *is* listening, currently. Where is that set? Localhost would work if you are sure that goes back to Hyperkitty. Chances are you are hosting multiple websites and using virtual server
On 05/12/2018 06:03 PM, Eric Abrahamsen wrote: sections, so localhost will most probably not end up at Hyperkitty itself.
I would use the external facing url of hyperkitty and use https. You'll have to add your public ip addresses to MAILMAN_ARCHIVER_FROM in the frontends settings.
If you are serving the frontend using tcp sockets you might be able to use localhost with the port number, but I'd suggest using the external address since that should always work and is less likely to change