Okay,
I have mailman3 working to allow me to send/receive emails. postorius seems to be working fine. My only issue seems to be with hyperkitty saving the archive.
postorius seems to be working fine. Hyperkitty on the other hand is failing.
I have nginx running with multiple website being serviced from the same server.
I updated the config where port 80 gets redirected to SSL.
I tried setting mailman3-hyperkitty.conf to both:
base_url: http://localhost/hyperkitty/ base_url: https://lists.domain.com/hyperkitty/
But neither seem to be working. Does hyperkitty require traffic to be going over port 80?
-- Thank you Samir Faci https://keybase.io/csgeek
On 5/4/20 6:11 PM, Samir Faci wrote:
I have nginx running with multiple website being serviced from the same server.
I updated the config where port 80 gets redirected to SSL.
I tried setting mailman3-hyperkitty.conf to both:
base_url: http://localhost/hyperkitty> base_url: https://lists.domain.com/hyperkitty/
Either should be OK, possibly dependent of your nginx config.
But neither seem to be working. Does hyperkitty require traffic to be going over port 80?
No. https should work. Can you go to https://lists.domain.com/hyperkitty/ in a browser?
Do you have api_key: set in mailman3-hyperkitty.conf and is it set to the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django settings.
Note the value needs to be quoted in
MAILMAN_ARCHIVER_KEY = 'the_value'
and not in
api_key: the_value
because the former is a Python string and the latter is a config value.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Sorry about this, I had a draft ready to go sitting there for the past few hours.
I stand corrected. I'm not sure what combinations of factors fixed this but it's all good now.
base_url: https://lists.domain.org/hyperkitty/ worked. I have an archive and about 50 emails of me talking to myself while testing all this out.
Thank you for all the help Marc and everyone else on the list.
-- Samir Faci
On Mon, May 4, 2020 at 7:36 PM Mark Sapiro <mark@msapiro.net> wrote:
On 5/4/20 6:11 PM, Samir Faci wrote:
I have nginx running with multiple website being serviced from the same server.
I updated the config where port 80 gets redirected to SSL.
I tried setting mailman3-hyperkitty.conf to both:
base_url: http://localhost/hyperkitty> base_url:
https://lists.domain.com/hyperkitty/
Either should be OK, possibly dependent of your nginx config.
But neither seem to be working. Does hyperkitty require traffic to be going over port 80?
No. https should work. Can you go to https://lists.domain.com/hyperkitty/ in a browser?
Do you have api_key: set in mailman3-hyperkitty.conf and is it set to the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django settings.
Note the value needs to be quoted in
MAILMAN_ARCHIVER_KEY = 'the_value'
and not in
api_key: the_value
because the former is a Python string and the latter is a config value.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Thank you Samir Faci https://keybase.io/csgeek
participants (2)
-
Mark Sapiro -
Samir Faci