Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)
On 6/6/24 11:22 AM, Marcus Bautze wrote:
Hi,
Sorry, that was a wrong information in my mail . I already changed the base url to your suggestion as I wrote the mail (and forgot to change it in the mail) but i‘m getting the same error :-(
I have some questions.
At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... you say "Thank you, archiver is now starting. Now there's another problem:". Does this mean messages are being archived in HyperKitty or are they accumulating in (I think the Debian path is) /var/lib/mailman/archives/hyperkitty/spool/?
At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys." To be clear, in mailman-web.py the key is quoted and in mailman-hyperkitty.cfg it is not. E.g., in mailman-hyperkitty.cfg
api_key: Some_key
and in mailman-web.py
MAILMAN_ARCHIVER_KEY = 'Some_key'
What are your versions for mailman-hyperkitty and HyperKitty? HyperKitty
= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 and if I recall corectly, at least one Debian package was shipped with this incompatibility
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
Am 07.06.2024 um 06:22 schrieb Mark Sapiro:
At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... you say "Thank you, archiver is now starting. Now there's another problem:". Does this mean messages are being archived in HyperKitty or are they accumulating in (I think the Debian path is) /var/lib/mailman/archives/hyperkitty/spool/?
They are in /var/lib/mailman3/archives/hyperkitty/spool/, i doesn't find them in the HyperKitty-archives.
At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys." To be clear, in mailman-web.py the key is quoted and in mailman-hyperkitty.cfg it is not. E.g., in mailman-hyperkitty.cfg
api_key: Some_key
here is the key unquoted:
api_key: ***
and in mailman-web.py
MAILMAN_ARCHIVER_KEY = 'Some_key'
here's the Key quoted:
MAILMAN_ARCHIVER_KEY = '***'
What are your versions for mailman-hyperkitty and HyperKitty? HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 and if I recall corectly, at least one Debian package was shipped with this incompatibility
i found:
python3-django-hyperkitty 1.3.7-1 python3-mailman-hyperkitty 1.2.1-1 mailman3-full 3.3.8-2~deb12u1
(no other hyperkitty-related packages)
-- Marcus Bautze marcus@mbautze.de
On 6/11/24 6:47 AM, Marcus Bautze via Mailman-users wrote:
i found:
python3-django-hyperkitty 1.3.7-1 python3-mailman-hyperkitty 1.2.1-1 mailman3-full 3.3.8-2~deb12u1
These versions should be OK and your other settings seem OK. I suspect
that the issue may be nginx not forwarding the Authorization: header
from mailman_hyperkitty. Your nginx config posted at
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
seems a bit off. If you compare that to
https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configurat...
you'll see you are missing a location /static/ directive and you've
included proxy_hide_header upgrade;. I'm not sure why you have this.
I don't see why ngnix would be dropping the Authorization: header , but
you might try adding proxy_pass_header "Authorization";
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Teilnehmer (2)
-
Marcus Bautze -
Mark Sapiro