Open tobald opened 1 year ago
Hello
Just tried to install on AlternC 3.5, during installation I've got these error :
Looks a trouble with hyperkitty package not installed before and have a trouble with key :
Paramétrage de python3-django-allauth (0.38.0+ds-1) ...
Paramétrage de python3-mailman-hyperkitty (1.1.0-9) ...
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/db/backends/postgresql/base.py", line 21, in <module>
import psycopg2 as Database
ModuleNotFoundError: No module named 'psycopg2'
And sql script looks duplicated
Running upgrade script 2.3.sh
Removing apache2 conf files from former alternc-mailman packages:
Running upgrade script 3.6.0.sh
ERROR 1060 (42S21) at line 2: Duplicate column name 'mailman_version'
Hello
After a moment, administration page from panel is operationnal but account is not logged. And I can't connect as admin. owner alias is working
Looks a trouble on /etc/mailman3/mailman-hyperkitty.cfg as base_url is set on localhost
base_url: http://localhost/mailman3/hyperkitty/
hi,
ModuleNotFoundError: No module named 'psycopg2'
Please install python3-psycopg2 and then apt install -f
.
Postgresql libraries should not be required though, see debian/alternc-mailman-config.postinst:mailman3-web mailman3-web/database-type select mysql.
And sql script looks duplicated
Running upgrade script 2.3.sh Removing apache2 conf files from former alternc-mailman packages: Running upgrade script 3.6.0.sh ERROR 1060 (42S21) at line 2: Duplicate column name 'mailman_version'
Any chance you ran this upgrade script multiple times? Maybe alternc_status was not update, SELECT value FROM alternc_status WHERE name='alternc-mailman_version' ?
Hello
python3-psycopg2 is installed and install -f don't return any trouble.
I've ran only once apt install, to now all process was :
apt install ./alternc-mailman-config_3.6.5_all.deb
apt install ./alternc-mailman_3.6.5_all.deb
alternc.install -f
dpkg-reconfigure python3-mailman-hyperkitty
apt install python3-psycopg2
apt install -f
alternc_status return :
Hello
Subscription looks also broken. From mailman web interface I've tried to add account (as admnistration page is not active) I get a confirmation message after subscription at https://alternc/mailman3/postorius/lists/list_alternc/
Jun 19 11:50:18 alternc postfix/cleanup[4042277]: 87456320D92: milter-reject: END-OF-MESSAGE from localhost[::1]: 4.7.1 Service unavailable - try again later; from=<conseil-bounces@list_alternc> to=<my_mail> proto=ESMTP helo=<alternc>
Jun 19 11:50:18 alternc postfix/cleanup[4042277]: 87456320D92: milter-reject: END-OF-MESSAGE from localhost[::1]: 4.7.1 Service unavailable - try again later; from=<conseil-bounces@list_alternc> to=<my_mail> proto=ESMTP helo=<altrenc>
After a moment, administration page from panel is operationnal but account is not logged. And I can't connect as admin.
Note there is no single sign-on implemented, as stated in the panel on the mailing list administration page you probably need to create an account in postorius manually. During mailman3-full installation you should have been prompted for a creating a postorius administration account, else you should be able to add/modify web administration accounts using django commands : sudo -u www-data /usr/share/mailman3-web/manage.py
Please note mailman3 is very different from version 2 :
Looks a trouble on /etc/mailman3/mailman-hyperkitty.cfg as base_url is set on localhost
No trouble here, this url is intended for local access, please refer to upstream documentation.
4.7.1 Service unavailable
Looks like postfix is not properly configured(?), alternc-mailman3 includes some modifications for main.cf, please check debian/alternc-mailman.postinst and report if this can be improved. We currently have 2 buster and one bullseye instance running this configuration successfully, those where previously running the older alternc-mailman.
Please read project README and debian/NEWS, if your instance is running on debian buster you need some manually backported packages.
Cheers
Hello
Thanks for your reply. About 4.7.1 error, was related to opendkim. In some case template is not set correctly. And permission are broken between opendkim and root user.
I confirm backport repositories are enabled.
Hello
I'll propose to merge in next days. As look globally functionnal. Should be better to open specific issue on main branch.
In my part I have a new trouble when someone send a mail and mailing is set in CC some other mails are "translated" , domain are replaced by alternc server name.
I can sent a sample by direct mail.
Hello
I propose to merge your work. As this could be set in our experimental repository. Can you confirm me about debian support (stretch and buster) ? It's a requirement to update correctly debian/changelog et tag this version
Thank a lot
it works on buster and bullseye. I think it should work on stretch.
Hello
Language default is set to 'en', then we can have some trouble with charset is set to 'us-ascii'. European language and other in this case could be displayed with broken word with "?"
Could be interesting to set to utf8 default language.
To workaround I followed this exchange : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/NZ47KAZHH7QLZWKE4FCFS4Y7CY6UVHMX/
In my case was set to fr with
for list in $(ls /var/lib/mailman3/lists/); do mailman shell -l $list; done
m.preferred_language = 'fr';quit()
and updated /etc/mailman3/mailman.cfg
default_language: fr
Hi,
I think language selection is outside the scope of alternc-mailman because one might use non-french languages. In the installation notes we state "Mailman site owner email address and default language are set in /etc/mailman3/mailman.cfg". Did you experience trouble when migrating lists configuration from mailman2?
Yes I've use fr as sample, it's utf8, not ascii charset. In mailman list where I found this workaround is lituanian.
Global language configuration could be only sysadmin context , in this case package don't need to care about it.
But when an user from its panel enable a new list could be interesting to use an override language. Without more idea, I think:
My tries were with new lists. Then I've not idea how is it when we upgrade a list.
this adds compatibility/migration path for mailman3 lists, and keeps mailman2 installation working.
this is a follow up for https://github.com/AlternC/alternc-mailman/pull/45 after branch rename.