Hi,
Where on the web interface is it possible to see the list of subscribers of a mailing list please?
TIA for any hint,
Peter
On 02/02/2018 01:24 PM, Peter Münster wrote:
Where on the web interface is it possible to see the list of subscribers of a mailing list please?
Since this is a Mailman 3 list I assume you're asking about Mailman 3/Postorius.
The short answer is it's a tab on the list's settings page, but you have to be a list or site admin to even see the tab.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, Feb 02 2018, Mark Sapiro wrote:
Where on the web interface is it possible to see the list of subscribers of a mailing list please?
The short answer is it's a tab on the list's settings page, but you have to be a list or site admin to even see the tab.
Yes, the question is rather: where can *normal* members (or moderators) can see the subscriber list?
-- Peter
On 02/02/2018 02:50 PM, Peter Münster wrote:
Yes, the question is rather: where can *normal* members (or moderators) can see the subscriber list?
Currently, they can't. If you think they should be able to, you can file an issue at <https://gitlab.com/mailman/postorius/issues/new>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, Feb 02 2018, Mark Sapiro wrote:
Yes, the question is rather: where can *normal* members (or moderators) can see the subscriber list?
Currently, they can't. If you think they should be able to, you can file an issue at <https://gitlab.com/mailman/postorius/issues/new>.
Thanks. Done.
It seems, that even the owner of the list cannot get the full names of the subscribers, only the email addresses. Is there any other possibility for the owner (or the site admin) to get the subscriber list with full names (perhaps with some Python scripting)?
TIA for any help,
Peter
On Fri, Feb 02 2018, Mark Sapiro wrote:
Yes, the question is rather: where can *normal* members (or moderators) can see the subscriber list? Currently, they can't. If you think they should be able to, you can file an issue at <https://gitlab.com/mailman/postorius/issues/new>. Thanks. Done.
It seems, that even the owner of the list cannot get the full names of the subscribers, only the email addresses. Is there any other possibility for the owner (or the site admin) to get the subscriber list with full names (perhaps with some Python scripting)? You should be able to use mailmanclient to get a list of subscribers with names. Names are optional though, if people signup without them you won't be able to get them. Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if
On 02/04/2018 01:45 PM, Peter Münster wrote: there is one associated.
IIRC one person(postorius account) can also signup at different lists using different names (regardless of address). There was some discussion about names and potentially using the from header to populate the database but I don't remember the result...
On Sun, Feb 04 2018, Simon Hanna wrote:
You should be able to use mailmanclient to get a list of subscribers with names.
It seems, that mailmanclient does not know about the real name (the first name and the last name in Django). But this seems to work:
from django.contrib.auth.models import User user = User.objects.get(email='address@of.user') print(user.first_name) print(user.last_name)
So, I'll try to make some loop over a list with email addresses, that I can get on the web interface.
Names are optional though, if people signup without them you won't be able to get them.
My usage of mailman is perhaps a bit special: users can't sign up, only the site owner signs up manually with create_user(email=, first_name=...) Then the site owner creates the mailing lists and uses mass subscription (for example all members of a basketball team). At one moment, the list of subscribers should be verified by all members, just to be sure, that nobody got forgotten.
Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if there is one associated.
Thanks. It would be nice, to see the first_name and the last_name of the django-auth user object.
IIRC one person(postorius account) can also signup at different lists using different names (regardless of address).
You mean the "display_name" of mailmanclient here? I won't use it. For my usage, I prefer a clear association of email, first name and last name in one account, no need for "display_name" here.
There was some discussion about names and potentially using the from header to populate the database but I don't remember the result...
Nice idea, especially for the normal use case, the public mailing list (but not for mine).
Off topic: I have "Receive own postings = Yes", but I don't receive copies of my postings to this list...
Kind regards,
PeterOn 02/04/2018 11:37 AM (UTC -0800), Peter Münster wrote:
On Sun, Feb 04 2018, Simon Hanna wrote:
IIRC one person(postorius account) can also signup at different lists using different names (regardless of address).
You mean the "display_name" of mailmanclient here? I won't use it. For my usage, I prefer a clear association of email, first name and last name in one account, no need for "display_name" here.
This would seem to be specific to your use case. I think in general what we would want to display is the display_name from the list's member record.
Off topic: I have "Receive own postings = Yes", but I don't receive copies of my postings to this list...
We tried to send your copy of your post to you, but your MTA called it spam.
Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: to=<pmlists@free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command))
(time stamp is UTC -0000)
I suspect it doesn't like the fact that it's From: you but not sent by your server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02/04/2018 10:31 PM, Mark Sapiro wrote:
On 02/04/2018 11:37 AM (UTC -0800), Peter Münster wrote:
Off topic: I have "Receive own postings = Yes", but I don't receive copies of my postings to this list...
We tried to send your copy of your post to you, but your MTA called it spam.
Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: to=<pmlists@free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command))
(time stamp is UTC -0000)
I suspect it doesn't like the fact that it's From: you but not sent by your server.
It looks like you bounce all your own posts
select email, timestamp from bounceevent where email = 'pmlists@free.fr';
email | timestamp-----------------+---------------------------- pmlists@free.fr | 2018-01-25 21:43:28.881213 pmlists@free.fr | 2018-01-25 23:08:27.943445 pmlists@free.fr | 2018-01-26 08:10:54.681684 pmlists@free.fr | 2018-01-26 08:36:54.613672 pmlists@free.fr | 2018-01-26 10:20:43.226199 pmlists@free.fr | 2018-01-26 12:13:49.488949 pmlists@free.fr | 2018-01-28 16:32:49.927769 pmlists@free.fr | 2018-01-28 20:15:21.073091 pmlists@free.fr | 2018-01-28 20:27:59.060866 pmlists@free.fr | 2018-01-28 21:23:54.176886 pmlists@free.fr | 2018-01-29 17:16:42.710431 pmlists@free.fr | 2018-01-30 08:17:39.112296 pmlists@free.fr | 2018-01-31 07:39:00.954735 pmlists@free.fr | 2018-01-31 08:41:45.46342 pmlists@free.fr | 2018-01-31 11:00:29.281051 pmlists@free.fr | 2018-01-31 19:58:17.341603 pmlists@free.fr | 2018-01-31 20:09:41.194564 pmlists@free.fr | 2018-01-31 20:59:58.868911 pmlists@free.fr | 2018-02-02 21:24:44.263614 pmlists@free.fr | 2018-02-02 22:51:04.674311 pmlists@free.fr | 2018-02-04 12:45:33.179401 pmlists@free.fr | 2018-02-04 19:38:10.224125 (22 rows)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, Feb 04 2018, Mark Sapiro wrote:
This would seem to be specific to your use case. I think in general what we would want to display is the display_name from the list's member record.
Ok, I see. Now I know, how to generate such list (email + full name) as site administrator, so it's ok for me.
We tried to send your copy of your post to you, but your MTA called it spam.
Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: to=<pmlists@free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command))
IMO, spam filtering should be done at user level, every user should be free to filter what he likes, not the MTA. Perhaps I should do it like you, and manage my own email relay host? I've tried to subscribe with an address at orange.fr but it does not seem to work, probably the same problem as with free.fr...
-- Peter
On Sun, Feb 04 2018, Simon Hanna wrote:
You should be able to use mailmanclient to get a list of subscribers with names. It seems, that mailmanclient does not know about the real name (the first name and the last name in Django). But this seems to work:
from django.contrib.auth.models import User user = User.objects.get(email='address@of.user') print(user.first_name) print(user.last_name)
So, I'll try to make some loop over a list with email addresses, that I can get on the web interface. These are names that are saved in Postorius' (django) database and have nothing to do with mailman. Furthermore you will only find them if people have logins for the frontend. They don't have to. Also these names are optional. They aren't populated during signup and
On 02/04/2018 08:37 PM, Peter Münster wrote: people have to provide them afterwards themselves.
Names are optional though, if people signup without them you won't be able to get them. My usage of mailman is perhaps a bit special: users can't sign up, only the site owner signs up manually with create_user(email=, first_name=...) Then the site owner creates the mailing lists and uses mass subscription (for example all members of a basketball team). At one moment, the list of subscribers should be verified by all members, just to be sure, that nobody got forgotten.
Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if there is one associated. Thanks. It would be nice, to see the first_name and the last_name of the django-auth user object.
IIRC one person(postorius account) can also signup at different lists using different names (regardless of address). You mean the "display_name" of mailmanclient here? I won't use it. For my usage, I prefer a clear association of email, first name and last name in one account, no need for "display_name" here. Displaying the names stored in django probably won't happen. Matching the names in django with the members in lists would require lots of code where people can just supply their name when they signup for a list. Also you might want to be known by name on one list and not on others...
On Mon, Feb 05 2018, Simon Hanna wrote:
from django.contrib.auth.models import User user = User.objects.get(email='address@of.user') print(user.first_name) print(user.last_name)
So, I'll try to make some loop over a list with email addresses, that I can get on the web interface.
These are names that are saved in Postorius' (django) database and have nothing to do with mailman.
I know, but for my use case, it's just what I want, and it seems to work.
Displaying the names stored in django probably won't happen. Matching the names in django with the members in lists would require lots of code
Really? I don't know Python, but wouldn't it be possible (just as an option) to do something like this:
user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name
If there is no Django account associated to the email address, the columns would just be empty.
I think, that my use case is perhaps not so special: whenever you manage a sports club, you'll need lists like
- members@my-club.com
- board@my-club.com
- team-1@my-club.com
- team-2@my-club.com
- and so on
Whenever there is a new member, the administrator will do the sign up with create_user(...) and subscribe him to the right lists. And the members (or the moderators) should be able to check the subscriber list sometimes.
-- Peter
Displaying the names stored in django probably won't happen. Matching the names in django with the members in lists would require lots of code Really? I don't know Python, but wouldn't it be possible (just as an option) to do something like this:
user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name
Yeah, that way you make quite a lot of database queries. to make it perform better, you'd need to get all user accounts and match them to the subscribers. Since users can have multiple addresses you need to check all their addresses.
Making this quite expensive for a very small use case.
On Tue, Feb 06 2018, Simon Hanna wrote:
user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name
Yeah, that way you make quite a lot of database queries.
Is this a problem? Let's say, only moderators can see such a list. And I guess, that they won't do it so often, that the server crashes...
Could you please show me, where I should add these 3 lines, so that I can patch my local mailman installation?
TIA,
PeterOn 02/06/2018 09:13 PM, Peter Münster wrote:
On Tue, Feb 06 2018, Simon Hanna wrote:
user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name
Yeah, that way you make quite a lot of database queries. Is this a problem? Let's say, only moderators can see such a list. And I guess, that they won't do it so often, that the server crashes...
Could you please show me, where I should add these 3 lines, so that I can patch my local mailman installation?
TIA, You will need to patch the list_member_view in views/list.py to pass along all relevant information to the template which is templates/postorius/lists/members.html
participants (4)
-
Mark Sapiro -
Peter Münster -
Peter Münster -
Simon Hanna