Greetings,
I'm finding something a bit odd with our listserv. Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled).
If I select Enabled and Save, then delivery starts working for that user.
There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run:
mailman members --nomail any listname@listserv
Nothing is returned.
If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great.
Thanks!
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856
phirayam@fredhutch.org<mailto:phirayam@fredhutch.org>
On 12/9/24 17:35, Hirayama, Pat wrote:
Greetings,
I'm finding something a bit odd with our listserv.
Please see https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv
Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled).
If you look in the MTA logs is mail being sent to them.
As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.py...
Also see the various tabs at https://www.example.com/mailman3/accounts/subscriptions/
If I select Enabled and Save, then delivery starts working for that user.
This should only happen if the users address or user based preference or the global preference is Disabled.
There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run:
mailman members --nomail any listname@listserv
Nothing is returned.
Because all members ultimately have delivery enabled.
If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great.
It shouldn't be necessary to do that. For one of these members, e.g. user@example.com, that isn't getting mail, do this in mailman shell
mailman shell -l list@example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the list@example.com mailing list
>>> from mailman.core.constants import system_preferences
>>> mbr = m.members.get_member('user@example.com')
>>> print(mbr.delivery_status)
(this will print the ultimate delivery_status, for the components do)
>>> print(mbr.preferences.delivery_status)
(output)
>>> print(mbr.address.preferences.delivery_status)
(output)
>>> print(mbr.address.user.preferences.delivery_status)
(output)
>>> print(system_preferences.delivery_status)
(output)
>>>
The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Apologies, I should've said my "Mailman 3" server, not listserv.
MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs.
As for the CLI commands, I keep getting Attribute Error when I try them, like:
/opt/mailman # mailman shell -l listname@mailman.tld Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the listname@mailman.tld mailing list
from mailman.core.constants import system_preferences mbr = m.members.get_member('user@domain.com.') print(mbr.delivery_status) Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'delivery_status'
Thanks,
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org
From: Mark Sapiro <mark@msapiro.net> Sent: Monday, December 9, 2024 18:38 To: mailman-users@mailman3.org <mailman-users@mailman3.org> Subject: [MM3-users] Re: Enable delivery
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 12/9/24 17:35, Hirayama, Pat wrote:
Greetings,
I'm finding something a bit odd with our listserv.
Please see https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20L...
Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled).
If you look in the MTA logs is mail being sent to them.
As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://urldefense.com/v3/__https://gitlab.com/mailman/mailman/-/blob/master...
Also see the various tabs at https://urldefense.com/v3/__https://www.example.com/mailman3/accounts/subscr...
If I select Enabled and Save, then delivery starts working for that user.
This should only happen if the users address or user based preference or the global preference is Disabled.
There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run:
mailman members --nomail any listname@listserv
Nothing is returned.
Because all members ultimately have delivery enabled.
If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great.
It shouldn't be necessary to do that. For one of these members, e.g. user@example.com, that isn't getting mail, do this in mailman shell
mailman shell -l list@example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the list@example.com mailing list
>>> from mailman.core.constants import system_preferences
>>> mbr = m.members.get_member('user@example.com')
>>> print(mbr.delivery_status)
(this will print the ultimate delivery_status, for the components do)
>>> print(mbr.preferences.delivery_status)
(output)
>>> print(mbr.address.preferences.delivery_status)
(output)
>>> print(mbr.address.user.preferences.delivery_status)
(output)
>>> print(system_preferences.delivery_status)
(output)
>>>
The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailma... Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailman...
This message sent to phirayam@fredhutch.org
On 12/10/24 10:43, Hirayama, Pat wrote:
Apologies, I should've said my "Mailman 3" server, not listserv.
MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs.
As for the CLI commands, I keep getting Attribute Error when I try them, like:
/opt/mailman # mailman shell -l listname@mailman.tld Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the listname@mailman.tld mailing list
from mailman.core.constants import system_preferences mbr = m.members.get_member('user@domain.com.') print(mbr.delivery_status) Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'delivery_status'
Are you literally typing
mbr = m.members.get_member('user@domain.com.')
That needs to be an actual list member's email without a trailing period. The fact that mbr is None means whatever you provided is not a member of the listname@mailman.tld list.
Curious that the member(s) in question are not amongst the recipients delivered to the MTA even though
when I run:
mailman members --nomail any listname@listserv
Nothing is returned.
This should only happen if the members are digest members (are they) or are directly addressed in To: or Cc: of the post.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
No, I was obfuscating the addresses of the user and listname. And it was the trailing dot/period that was the problem. Sorry about that -- copy/pasting from the emailed report rather than typing the address myself.
Now that I have the commands and order, I will look closer at some of those lists when additional reports come in.
Thank you!
-p-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Tuesday, December 10, 2024 1:41 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: Enable delivery
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 12/10/24 10:43, Hirayama, Pat wrote:
Apologies, I should've said my "Mailman 3" server, not listserv.
MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs.
As for the CLI commands, I keep getting Attribute Error when I try them, like:
/opt/mailman # mailman shell -l listname@mailman.tld Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the listname@mailman.tld mailing list
from mailman.core.constants import system_preferences mbr = m.members.get_member('user@domain.com.') print(mbr.delivery_status) Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'delivery_status'
Are you literally typing
mbr = m.members.get_member('user@domain.com.')
That needs to be an actual list member's email without a trailing period. The fact that mbr is None means whatever you provided is not a member of the listname@mailman.tld list.
Curious that the member(s) in question are not amongst the recipients delivered to the MTA even though
when I run:
mailman members --nomail any listname@listserv
Nothing is returned.
This should only happen if the members are digest members (are they) or are directly addressed in To: or Cc: of the post.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mail man- users.mailman3.org/__;!!GuAItXPztq0!kBv3nt9E96ao_7FvkLnOsm_R9OWol1 U4Lk0bnfCxTPiRuYdCv4jHRpx11tT3vx2cyFNW8ByfZlsvtwg$ Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma n- users@mailman3.org/message/ET7NTZVDLCY6RBXHUIYRVTYQQX6SQ3KI/__; !!GuAItXPztq0!kBv3nt9E96ao_7FvkLnOsm_R9OWol1U4Lk0bnfCxTPiRuYdCv4 jHRpx11tT3vx2cyFNW8ByfwPhcXNc$
This message sent to phirayam@fredhutch.org
participants (2)
-
Hirayama, Pat -
Mark Sapiro