restrict sending to owner/moderator
by m.dohmen＠xconnect.de
Hello,
I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable.
Is there a way to do this?
2 hours, 38 minutes
Installing mm3 with docker
by Tom Browder
I am trying to follow instructions but when I get to the actual docker pull
command (with trust enabled):
# docker pull maxking/mailman-core:release
I get an error message:
No trust data for release
I have tried adding various tags but no changes.
What am I doing wrong?
Thanks.
-Tom
1 week, 2 days
Mailman 3 bounce handling and DKIM mitigation
by David Krantz
Hi,
I have a question on bounce handling. I get the impression that
bounces are just lost and neither handled nor forwarded to the list
admin. Is this a known problem? I am running mailman from git, but
about version 3.1 and use postfix. I find lots of things in the
bounceevents table. Is there any way to find out more on these events?
I probably can configure postfix to send listname-bounce@domain to an
admin adress. Or for that matter hack mailman to send it to the
correct admin.
Also the DKIM mitigation does not seem to detect DKIM domains. If I
force the mitigation for all mails it works but that of course has
annoying consequences although mostly cosmetic. This has caused quite
a number of bounces for my lists (as well as being temporarily banned
by at least Microsoft).
I'm thinking of upgrading to a later version. What is the latest
version that might be a good idea to install today? I install from
gitlab.
cheers
// David
1 week, 6 days
Social Auth, howto?
by Claus-Justus Heine
Hi,
sorry, this seems to be a Django stuff, but how do I enable this social
auth stuff? I get the following
Fedora: gives me a login screen (ok)
Yahoo: gives me a login screen and lots of commercials (ok)
OpenId: gives me a possibility to sign up or in (ok)
Github:
internal server error 500, Django log: DoesNotExist: SocialApp matching
query does not exist.
Same with GitLab and Google.
Ok, seemingly I need to do something to make it work, has anyone a link
to some snippet of documentation of example setup?
Thanks
Claus
--
Claus-Justus Heine himself(a)claus-justus-heine.de
http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
2 weeks, 2 days
Moderation requests, dash-board link in notification?
by Claus-Justus Heine
Hi there,
I suppose this is rather a simple configuration issue. However, with
Mailman v2 the moderator or list-owner was supplied with a link to the
admin-site in the moderation-reminder.
I suppose that this can also be very easily configured with v3?
Of course, I know where my amdin-site is, but I am planning to deploy
mm3 in a setting with educated dummy users which probably would rather
first ask and only try to find out by themselves if they cannot find
someone to ask.
Cheers
Claus
--
Claus-Justus Heine himself(a)claus-justus-heine.de
http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
2 weeks, 2 days
Funny responds to subscriptions emails
by Claus-Justus Heine
Playing around with mailman3 I get funny responds from the list-manager
to subscription requests. I have set up a "playground" list (guess why)
and trying to subscribe via email. Basically, things work. However, the
end-user (me) gets confusing responses. I would not care for myself, but ...
What I did: send an Email
> To: playground <playground-subscribe(a)lists.claus-justus-heine.de>
> From: Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE>
> Subject: Test
So far so good. I get the expected confirmation email with subject
confirm 3093b4 etc etc etc
But I also get a second rather confusing email:
> The results of your email command are provided below.
>
> - Original message details:
> From: Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE>
> Subject: Test
> Date: Sat, 2 Sep 2017 22:24:08 +0200
> Message-ID: <44151460-05a8-4c35-e0d4-646efe3cf234(a)IANS.Uni-Stuttgart.DE>
>
> - Results:
> Confirmation email sent to Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE>
> No such command: Test
> No such command: --=20
> No such command: Claus-Justus
> No such command: f=C3=BCr
> No such command: Numerische
> No such command: Stuttgart
> No such command: +49
> No such command: +49
>
> - Done.
BTW, I also got the same confusing email when subscribing to
mailman-users(a)mailman3.org (is attached).
Can this be switched off? I don't care for myself, but if you think that
this software is ready for production, then end-users should not receive
such kind of """"things""""
Regards
Claus
--
Claus-Justus Heine himself(a)claus-justus-heine.de
http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
2 weeks, 2 days
Help request, almost got it going, but ....
by Claus-Justus Heine
First: thanks for all those development work, I am aware of the fact
that this is free software and most of the development probably happened
in someones spare-time.
I have some problems:
- I tried to install mailman v3. "Read the (non) docs" was of little
help, but I got to some partly success following the commands in the
scripts in the docker image at
https://github.com/maxking/docker-mailman
Things seemed to work out, I generated a test-list "Playground" and now
I am just in the progress to click through all the configuration options
in the the postorius Web-GUI. So far so good
Now I read the "Message Acceptance" tab AND here is the problem:
Seemingly, at some point in the deep dungeons of the source code the
"Acceptable aliases" Text-Box is not interpreted correctly.
Specifically, at the start it contains the string
[]
When then changing something int the "Message Acceptance" tab, an error
shows up in the web-page (but no-where in the logs)
"An error occured: []"
and the bogus [] is restored. I tried to dig into the source code, and
well, the data source of the text-field is an array or list of
acceptable email-adresses. But seemingly finally at some point in the
source code an empty list is not converted to the empty string, but to
the string [].
I can get rid of the error message "An error occured: []" by inserting
an email-at '@' at just some place in the input box, this yields
(clicking "Save changes" again and againg ...):
[u"[u'@']"]
[u'[u\'[u"[u\\\'@\\\']"]\']']
[u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']']
and so on.
Unfortunately, I did not find the location of this bug, although I was
finally able to add some "foobar" string to the already bogus web-output.
Any help would be appreciated.
BTW:
* where is the bug-tracker for mailman3?
* The documentation is really, well, close to non existent. Personally,
I think the name of the URL "read-the-docs" is almost cynical.
Guess I give up on it, it just does not seem to be ready for production.
This was (following the docker stuff at githb) with
Pythong3:
mailman==3.1.0
mailman-hyperkitty==1.1.0
Python2:
mailmanclient==3.1.0
postorius==1.1.0
hyperkitty==1.1.1
django-mailman3==1.1.0
Here I realize a slight version difference between the hyperkitty stuff.
But this is a bug in postorius. So what.
Thanks for any help, cheers
Claus
--
Claus-Justus Heine himself(a)claus-justus-heine.de
http://www.claus-justus-heine.de/
Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de
2 weeks, 3 days
HyperKitty: Thread matching query does not exist
by C. R. Oldham
Greetings,
I have an active list for which I am trying to debug some deliverability
issues. When a user tells me that folks aren't getting their postings, I
check the archives first. In this case, I am getting a traceback saying
"thread matching query does not exist" when I try to go to the HyperKitty
page for the list. How can I debug this?
I am using Mailman 3 via the Docker containers documented here:
https://asynchronous.in/docker-mailman/
The container versions appear to be 0.1.
--cro
2 weeks, 4 days
