Hello,
I installed mailman3 on debian through the command:
$ aptitude install mailman3-full
does it need to do further config following http://docs.mailman3.org/en/latest/config-core.html and http://docs.mailman3.org/en/latest/config-web.html ? where is manage.py and settings.py if install from the above command line?
or it is already well configued to use? If yes, how to visit the frontend page?
I try to follow http://docs.mailman3.org/en/latest/userguide.html, but it is not so straightforward. During installation thru the command line, it did not ask for creating the first list, so do not know how to change LISTNAME.DOMAIN in http://WEBSERVER/mailman3/lists/LISTNAME.DOMAIN. .
Thank you and regards,
Rex
On 04/20/2018 09:58 PM, 孙志勇 wrote:
I installed mailman3 on debian through the command:
$ aptitude install mailman3-full
does it need to do further config following http://docs.mailman3.org/en/latest/config-core.html and http://docs.mailman3.org/en/latest/config-web.html ? where is manage.py and settings.py if install from the above command line?
You should be following Debian's documentation. If that doesn't exist or you can't find it, you need to take that up with Debian.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
孙志勇 writes:
I installed mailman3 on debian through the command:
$ aptitude install mailman3-full
does it need to do further config
As usual, Mark beat me to it. I have some advice to add:
First, look for /usr/share/doc/mailman3/README.Debian or a similarly named file. I would expect to find documentation explaining how to get started, specifically for the standard Debian setup, there.
You may get an answer here, so check back in a couple of days, but as Mark said, since a Debian package is supposed to be configured through the package manager, this is properly a question for a Debian channel.
following http://docs.mailman3.org/en/latest/config-core.html and http://docs.mailman3.org/en/latest/config-web.html ?
Unless you are sophisticated in installing software and know your Debian system well, DO NOT try to follow those instructions by yourself. Mixing our instructions with a Debian package install may create a big mess.
tl;dr: Mailman's generic documentation assumes a "vanilla Unix" system, and does not necessarily conform to Debian's interpretation of the Filesystem Hierarchy Standard and other parts of the Linux Standard Base. There is no guarantee that Debian's package corresponds to the version described in "latest", especially not in locations of various files. There is no guarantee that Debian's configuration of the webserver looks anything like our generic configuration, which is similar to the real configuration of the Mailman 3 server we use.
or it is already well configued to use? If yes, how to visit the frontend page?
These are also Debian questions, and should be answered by the resources mentioned previously.
Regards,
-- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
OK, I follow the instruction of /usr/share/doc/mailman3/README.Debian,
it can visit http://server/mailman3/postorius/lists/, but when login, it says Sever Error (500). in /var/log/mailman3/web/mailman-web.log there is a line: SMTPRecipientsRefused: {u'xxx@xx.com': (451, '4.3.0 <xxx@xx.com>: Temporary lookup failure')} # xxx@xx.com is superuser email address.
in postfix log file, there is: Apr 22 18:05:53 mail postfix/smtpd[12870]: error: open database /var/lib/mailman3/data/postfix_domains.db: No such file or directory Apr 22 18:05:53 mail postfix/smtpd[12870]: error: open database /var/lib/mailman3/data/postfix_lmtp.db: No such file or directory
how to solve it?
thank you.
------------------ Original ------------------ From: "Stephen J. Turnbull"<turnbull.stephen.fw@u.tsukuba.ac.jp>; Date: Sun, Apr 22, 2018 00:42 AM To: "孙志勇"<455750938@qq.com>; Cc: "mailman-developers"<mailman-developers@python.org>; Subject: [Mailman-Developers] mailman3 on debian
孙志勇 writes:
I installed mailman3 on debian through the command:
$ aptitude install mailman3-full
does it need to do further config
As usual, Mark beat me to it. I have some advice to add:
First, look for /usr/share/doc/mailman3/README.Debian or a similarly named file. I would expect to find documentation explaining how to get started, specifically for the standard Debian setup, there.
You may get an answer here, so check back in a couple of days, but as Mark said, since a Debian package is supposed to be configured through the package manager, this is properly a question for a Debian channel.
following http://docs.mailman3.org/en/latest/config-core.html and http://docs.mailman3.org/en/latest/config-web.html ?
Unless you are sophisticated in installing software and know your Debian system well, DO NOT try to follow those instructions by yourself. Mixing our instructions with a Debian package install may create a big mess.
tl;dr: Mailman's generic documentation assumes a "vanilla Unix" system, and does not necessarily conform to Debian's interpretation of the Filesystem Hierarchy Standard and other parts of the Linux Standard Base. There is no guarantee that Debian's package corresponds to the version described in "latest", especially not in locations of various files. There is no guarantee that Debian's configuration of the webserver looks anything like our generic configuration, which is similar to the real configuration of the Mailman 3 server we use.
or it is already well configued to use? If yes, how to visit the frontend page?
These are also Debian questions, and should be answered by the resources mentioned previously.
Regards,
-- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
On 04/22/2018 03:31 AM, 孙志勇 wrote:
it can visit http://server/mailman3/postorius/lists/, but when login, it says Sever Error (500). in /var/log/mailman3/web/mailman-web.log there is a line: SMTPRecipientsRefused: {u'xxx@xx.com': (451, '4.3.0 <xxx@xx.com>: Temporary lookup failure')} # xxx@xx.com is superuser email address.
in postfix log file, there is: Apr 22 18:05:53 mail postfix/smtpd[12870]: error: open database /var/lib/mailman3/data/postfix_domains.db: No such file or directory Apr 22 18:05:53 mail postfix/smtpd[12870]: error: open database /var/lib/mailman3/data/postfix_lmtp.db: No such file or directory
Please report these issues to Debian. Otherwise their package/documentation won't get fixed.
That said, the above errors are because Postfix can't send mail and there are no Mailman specific Postfix alias files. This is because you haven't yet created a list.
Try
mailman aliases
This should create the /var/lib/mailman3/data/postfix_domains.db and /var/lib/mailman3/data/postfix_lmtp.db files.
Fixing this may fix the 500 error. If not, we need more info as to what the issue is. There may be a more detailed error in the web server's error log or in mailman's log. The latter might be in /var/lib/mailman3/logs/ or probably somewhere in /var/log/mailman3/ depending on how Debian set this up.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Thank you.
Yesterday someone from debian list replied me, he asked to do:
$ touch /var/lib/mailman3/data/postfix_{domains,lmtp} $ chmod 660 /var/lib/mailman3/data/postfix_{domains,lmtp} $ chown list:list /var/lib/mailman3/data/postfix_{domains,lmtp} $ postmap /var/lib/mailman3/data/postfix_{domains,lmtp}
and then it works, I think your solution: $ mailman aliases should also work.
------------------ Original ------------------ From: "Mark Sapiro"<mark@msapiro.net>; Date: Sun, Apr 22, 2018 10:09 PM To: "mailman-developers"<mailman-developers@python.org>;
Subject: Re: [Mailman-Developers] mailman3 on debian
On 04/22/2018 03:31 AM, 孙志勇 wrote:
it can visit http://server/mailman3/postorius/lists/, but when login, it says Sever Error (500). in /var/log/mailman3/web/mailman-web.log there is a line: SMTPRecipientsRefused: {u'xxx@xx.com': (451, '4.3.0 <xxx@xx.com>: Temporary lookup failure')} # xxx@xx.com is superuser email address.
in postfix log file, there is: Apr 22 18:05:53 mail postfix/smtpd[12870]: error: open database /var/lib/mailman3/data/postfix_domains.db: No such file or directory Apr 22 18:05:53 mail postfix/smtpd[12870]: error: open database /var/lib/mailman3/data/postfix_lmtp.db: No such file or directory
Please report these issues to Debian. Otherwise their package/documentation won't get fixed.
That said, the above errors are because Postfix can't send mail and there are no Mailman specific Postfix alias files. This is because you haven't yet created a list.
Try
mailman aliases
This should create the /var/lib/mailman3/data/postfix_domains.db and /var/lib/mailman3/data/postfix_lmtp.db files.
Fixing this may fix the 500 error. If not, we need more info as to what the issue is. There may be a more detailed error in the web server's error log or in mailman's log. The latter might be in /var/lib/mailman3/logs/ or probably somewhere in /var/log/mailman3/ depending on how Debian set this up.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/455750938%40qq.co...
Security Policy: http://wiki.list.org/x/QIA9
On 04/22/2018 12:31 PM, 孙志勇 wrote:
OK, I follow the instruction of /usr/share/doc/mailman3/README.Debian,
it can visit http://server/mailman3/postorius/lists/, but when login, it says Sever Error (500). in /var/log/mailman3/web/mailman-web.log there is a line: SMTPRecipientsRefused: {u'xxx@xx.com': (451, '4.3.0 <xxx@xx.com>: Temporary lookup failure')} # xxx@xx.com is superuser email address. Did you use a valid email address? From what you describe what is happening is that the frontend is trying to confirm your email address but can't deliver it. It might also be a configuration issue with the MTA you are using. Try to send an email to that address from the command line on the server.
To work around this particular issue you could do the following: open a django shell (I don't know where debian puts the manage.py file, but you should have one): python manage.py shell
in the shell do the following: from allauth.account.models import EmailAddress e = EmailAddress.objects.get(email='xxx@xx.com') e.verified = True e.save()
Of course you need to replace the email, with the one you have used. That should mark the email as verified in the database and let you login. Note that this is sort of a hack and you should figure out what's going on there...
participants (4)
-
Mark Sapiro -
Simon Hanna -
Stephen J. Turnbull -
孙志勇