Hi all,
I want to update some list member's display_name either with mailman shell or mailmanclient. These mostly aren't users in Postorius so I only want to operate on the subscribed list member. I've tried everything I can find in the docs and am stuck.
I've tried using `user_manager.get_user()` and then updating `user.display_name` followed by a `commit()` but it doesn't seem to persist the change.
The `absorb_existing` flag for mailmanclient's `User.add_address()` looks promising but the docs read "It will import the existing user into the current one, not overwriting any previously set value." which in some cases, the member already has a display_name set. I haven't tried this yet.
I'd appreciate any help pointing in the right direction.
Thanks,
Nick
I'm in the process of setting up mailman3. The only problem I seem to be
having is getting Hyperkitty to archive messages. Rather than the
authorisation problems people have previously asked about on the list, I
am getting a 403 error...
Aug 05 15:38:40 2019 (10229) HyperKitty failure on
http://localhost/mailman3/hyperkitty/api/mailman/urls:
<html><title>Forbidden</title><body>
<h1>Access is forbidden</h1></body></html> (403)
Aug 05 15:38:58 2019 (10222) HyperKitty failure on
http://localhost/mailman3/hyperkitty/api/mailman/archive:
<html><title>Forbidden</title><body>
<h1>Access is forbidden</h1></body></html> (403)
Any suggestions would be appreciated.
Phil
hey, I have got a problem with flufl.lock in mailman3. When my server is rebooted, locked files seems to stay and cause errors so mailman3 core wont start (it is started automatically by supervisord service):
PermissionError: [Errno 1] Operation not permitted
Traceback (most recent call last):
File
"/home/user/.local/lib/python3.6/site-packages/mailman/bin/master.py",
line 146, in acquire_lock
lock = acquire_lock_1(force)
File
"/home/user/.local/lib/python3.6/site-packages/mailman/bin/master.py",
line 125, in acquire_lock_1
lock.lock(timedelta(seconds=0.1))
File
"/home/user/.local/lib/python3.6/site-packages/flufl/lock/_lockfile.py",
line 259, in lock
raise TimeOutError('Could not acquire the lock')
flufl.lock._lockfile.TimeOutError: Could not acquire the lock
I have to remove the files in var/locks manually to go forward. Is there a configuration error for my setup? Or is it just a not fixed bug?
Greetsn, jekyl
I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database.
https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…
If you use this and see needed corrections or additions, please let me know! ~Kelly
Hi,
I came across this really useful guide (posted to the list earlier). It has all gone really well and mailman 3 is installed. However, I have an issue, when I go to login using Postorius, I get the login page when I enter my credentials the page appears to hang and eventually goes to a Error 500 page. This totally hangs all of the mailman 3 web interface (but not apache). I then have to reboot the server to even get back to the login page.
Any tips please?
Thanks
So our mailman got stuck again, but I did follow your advise. Here's
what I've found:
On 3/29/19 2:58 PM, Mark Sapiro wrote:
> On 3/29/19 2:28 PM, Dmitry Makovey wrote:
>> I've had encountered this situation now twice: mail is being stuck in
>> "out" queue and nothing in the logs indicates the issue. Is there a way
>> to ask mailman-core politely to attempt delivery (perhaps with increased
>> debugging in the logs) *without* restarting the core (which does solve
>> *this* problem but creates other problems, like availability of the
>> mailman as a whole)
>
>
> Is the "out" runner running?
yes:
# docker top mailman-core | grep -F out:
100 21681 13215 0
Mar28 ? 01:14:16
/usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C
/etc/mailman.cfg
> ps -fwwA |grep runner=out
>
> If not, you should be able to start it as the Mailman user with a
> command like
>
> /path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg
> --runner=out:0:1
>
> See 'ps -fwwA|grep runner' for examples
>
> If the out runner is running, is there a file named *.bak along with all
> the *.pck files in queue/out/
there is one, yes:
# ls -l /srv/mail/mailman/core/var/queue/out/*.bak
-rw-rw---- 1 100 65533 21512 Apr 14 19:45
/srv/mail/mailman/core/var/queue/out/1555296331.8386078+2c905825b82708e5a682b872b0aff320c9dd0b2e.bak
what does it indicate and what should my steps be to resolve this (other
than restarting queues)?
> And if it's not, is there anything in Mailman's logs to indicate why it
> died?
>
> Also, 'mailman restart' should only take a matter of seconds, but if the
> out runner is running but not processing its queue, I think sending it a
> SIGINT should restart it.
SIGINT killed the process allright, but it didn't auto-respawn. I ended
up spawning it with:
/usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C
/etc/mailman.cfg
but soon realized it doesn't go to background nicely so I've nohup'ed it
in the end. but it did solve my problem.
--
Sr System and DevOps Engineer SoM IRT
I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example:
http://domaina.com/postorius/lists/
Only listnames(a)domaina.com show up.
http://domainb.com/postorius/lists/
Only listnames(a)domainb.com show up.
Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well.
Brian
hey folks,
I am struggling with my mailman server for quite some time now. I am on
3.3 and the out runner cannot sent emails any more. According to this
issue [1] I found out--by logging the exception as well--, that mailman
has this problem:
Mar 31 09:34:51 2020 (71057) ACCEPT: <c1e4aa1be5b61c289c69a66a6d55565333d5a35b.camel(a)rumpelsepp.org>
Mar 31 09:34:52 2020 (71079) Cannot connect to SMTP server 127.0.0.1 on port 25: [Errno 21] Is a directory: '/usr/lib/python3.8/site-packages/mailman/templates'
What the hell is going on here? ☹︎ any ideas what's wrong?
The runner doesn't try to connect to postfix, since it fails with a
strange template error.
Stefan
[1]: https://gitlab.com/mailman/mailman/-/issues/514
Hi.
I have the following displayed when I look at the "System Information"
in Postorius:
Mailman Core Version GNU Mailman 3.3.0 (La Villa Strangiato)
Mailman Core API Version 3.0
Mailman Core Python Version 3.7.6 (default, Dec 19 2019, 23:49:42)
[GCC 5.4.0 20160609]
What surprises me is the protocol version. I have tried to set the
protocol version to 3.1 in mailman core (which should be the latest
according to the documentation) and restarting both core and web but
that gives no effect. Normally I have not had any protocol version
defined. Everything seems to work just fine but something is strange,
either the documentation, my setup or mailman/postorius.
// David
