[Mailman-Users] Re: Digest on/off via email

[Mark Dale via Mailman-Users]

> On 10/20/21 7:59 PM, Mark Dale via Mailman-Users wrote:
>>
>> Hi,
>>
>> As a list-member I'm unable to turn off digest-mode via email.
>>
>> To: -request@lists.
>> Subject: set digest off
>>
>>
>> Mailman (v 2.1.34) replies with an email (The results of your email 
>> commands) but the digest mode does not get set to "Off".
>>
>>
>> 
>> 
>> The results of your email command are provided below. Attached is your
>> original message.
>>
>> - Results:
>>  Not authenticated 


==

> You have to authenticate before you can set any options. The part of the `set 
> help` you elided contains
> 
>     set authenticate  [address=]
>     To set any of your options, you must include this command first, along
>     with your membership password.  If you're posting from an address
>     other than your membership address, specify your membership address
>     with `address=' (no brackets around the email address, and no
>     quotes!).
> 
> 
> I.e. don't put the commands in the Subject:. In the body put
> 
> set authenticate 
> set digest off
> 
==

Many thanks once again Mark, that did the trick. 

I had indeed glossed over the "set help". It's the "bleedin' obvious" when it's 
pointed out. 


Best,
Mark

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Digest on/off via email

[Mark Sapiro]

On 10/20/21 7:59 PM, Mark Dale via Mailman-Users wrote:


Hi,

As a list-member I'm unable to turn off digest-mode via email.

To: -request@lists.
Subject: set digest off


Mailman (v 2.1.34) replies with an email (The results of your email commands) but the 
digest mode does not get set to "Off".




The results of your email command are provided below. Attached is your
original message.

- Results:
 Not authenticated



You have to authenticate before you can set any options. The part of the 
`set help` you elided contains


set authenticate  [address=]
To set any of your options, you must include this command 
first, along

with your membership password.  If you're posting from an address
other than your membership address, specify your membership address
with `address=' (no brackets around the email address, 
and no

quotes!).


I.e. don't put the commands in the Subject:. In the body put

set authenticate 
set digest off


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Digest on/off via email

[Mark Dale via Mailman-Users]

Hi,

As a list-member I'm unable to turn off digest-mode via email.

To: -request@lists.
Subject: set digest off


Mailman (v 2.1.34) replies with an email (The results of your email commands) 
but the digest mode does not get set to "Off".




The results of your email command are provided below. Attached is your
original message.

- Results:
Not authenticated
Usage:

set help
Show this detailed help.

...

set digest plain
set digest mime
set digest off
When the `digest' option is turned off, you will receive postings
immediately when they are posted.  Use `set digest plain' if instead
you want to receive postings bundled into a plain text digest
(i.e. RFC 1153 digest).  Use `set digest mime' if instead you want to
receive postings bundled together into a MIME digest.




There isn't any info in the Mailman error log as to why the digest mode did not 
get turned off, and the only hint I've spotted so far is in the mail log where 
it says: "delivered to command: /var/lib/mailman/mail/mailman request LISTNAME"




Oct 20 21:28:04 sfo postfix/local[30957]: 0C59141796: 
to=<***LISTNAME@list.***DOMAIN>, relay=local, delay=0.44, 
delays=0.38/0.01/0/0.05, dsn=2.0.0, status=sent (delivered to command: 
/var/lib/mailman/mail/mailman request LISTNAME)


Oct 20 21:28:16 sfo postfix/smtp[30959]: 86BD141796: to=, 
relay=mx01.posteo.de[185.67.36.62]:25, delay=10, delays=0.01/0.01/9/1.3, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4HZNy74yvcz11SZ)




I note that sending a request email with the subject as "set show" returns an 
email with the expected result and the mail log also shows "delivered to 
command: /var/lib/mailman/mail/mailman request LISTNAME" -- so I'm guessing 
there isn't a file permissions issue with /var/lib/mailman/mail/mailman.




The results of your email command are provided below. Attached is your
original message.

- Results:
Your current option settings:
ack off
digest plain
delivery on
myposts on
hide off
duplicates off
reminders on

- Done.




Any clues on where I should be looking to get the Digest on/off working via 
email (or if I missed a setting in the list's Administration page) would be 
greatly appreciated.


Thanks,
Mark

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Moderators and admins not getting notifications of held posts

[Bruce Johnson via Mailman-Users]

Thanks! I will try this!

On Oct 20, 2021, at 1:39 PM, Mark Sapiro 
mailto:m...@msapiro.net>> wrote:

On 10/20/21 12:58 PM, Bruce Johnson via Mailman-Users wrote:
Thinking more upon this I think this was why we originally had the email 
hostname set to the list server FQDN instead of our domain. originally mailman 
lived on our mail server, but got moved to a different system when we moved to 
Exchange for mail (and later on to O365)  We had to create weird distribution 
lists for all the lists ( ie: a DL 
t...@pharmacy.arizona.edu that has as it’s 
only member 
t...@lists.pharmacy.arizona.edu ) for 
everything to work.
This worked well for years until we moved to a new mail spam and security 
service and introduced stricter DMARC and DKIM settings for all our mail. This 
is what broke one of our larger lists (our alumni outreach list, and of course 
it’s Homecoming next week, and the last email resulted in 650+ bounces for 
DMARC failures..mostly from aol and yahoo. )
Is it possible to have the email addresses of the mailman administrivia 
addresses (-owner -bounces, etc) be the FQDN, but outgoing list traffic be set 
to just the domain?


You could try this patch

=== modified file 'Mailman/MailList.py'
--- old/Mailman/MailList.py 2020-05-18 17:01:51 +
+++ new/Mailman/MailList.py 2021-10-20 20:31:06 +
@@ -190,7 +190,8 @@
def getListAddress(self, extra=None):
if extra is None:
return '%s@%s' % (self.internal_name(), self.host_name)
-return '%s-%s@%s' % (self.internal_name(), extra, self.host_name)
+return '%s-%s@%s%s' % (self.internal_name(), extra, 'lists.',
+   self.host_name

# For backwards compatibility
def GetBouncesEmail(self):


And a similar patch to the get_site_email function in Mailman/Utils.py.

--
Mark Sapiro mailto:m...@msapiro.net>>The highway is 
for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- 
mailman-users@python.org
To unsubscribe send an email to 
mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
  https://mail.python.org/archives/list/mailman-users@python.org/

--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Moderators and admins not getting notifications of held posts

[Mark Sapiro]

On 10/20/21 12:58 PM, Bruce Johnson via Mailman-Users wrote:


Thinking more upon this I think this was why we originally had the email 
hostname set to the list server FQDN instead of our domain. originally mailman 
lived on our mail server, but got moved to a different system when we moved to 
Exchange for mail (and later on to O365)  We had to create weird distribution 
lists for all the lists ( ie: a DL t...@pharmacy.arizona.edu that has as it’s 
only member t...@lists.pharmacy.arizona.edu ) for everything to work.

This worked well for years until we moved to a new mail spam and security 
service and introduced stricter DMARC and DKIM settings for all our mail. This 
is what broke one of our larger lists (our alumni outreach list, and of course 
it’s Homecoming next week, and the last email resulted in 650+ bounces for 
DMARC failures..mostly from aol and yahoo. )

Is it possible to have the email addresses of the mailman administrivia 
addresses (-owner -bounces, etc) be the FQDN, but outgoing list traffic be set 
to just the domain?



You could try this patch

=== modified file 'Mailman/MailList.py'
--- old/Mailman/MailList.py 2020-05-18 17:01:51 +
+++ new/Mailman/MailList.py 2021-10-20 20:31:06 +
@@ -190,7 +190,8 @@
 def getListAddress(self, extra=None):
 if extra is None:
 return '%s@%s' % (self.internal_name(), self.host_name)
-return '%s-%s@%s' % (self.internal_name(), extra, self.host_name)
+return '%s-%s@%s%s' % (self.internal_name(), extra, 'lists.',
+   self.host_name

 # For backwards compatibility
 def GetBouncesEmail(self):


And a similar patch to the get_site_email function in Mailman/Utils.py.

--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Moderators and admins not getting notifications of held posts

[Bruce Johnson via Mailman-Users]

On Oct 20, 2021, at 12:58 PM, Bruce Johnson via Mailman-Users 
mailto:mailman-users@python.org>> wrote:

Thinking more upon this I think this was why we originally had the email 
hostname set to the list server FQDN instead of our domain. originally mailman 
lived on our mail server, but got moved to a different system when we moved to 
Exchange for mail (and later on to O365)  We had to create weird distribution 
lists for all the lists ( ie: a DL 
t...@pharmacy.arizona.edu
 that has as it’s only member 
t...@lists.pharmacy.arizona.edu
 ) for everything to work.

This worked well for years until we moved to a new mail spam and security 
service and introduced stricter DMARC and DKIM settings for all our mail. This 
is what broke one of our larger lists (our alumni outreach list, and of course 
it’s Homecoming next week, and the last email resulted in 650+ bounces for 
DMARC failures..mostly from aol and yahoo. )

Is it possible to have the email addresses of the mailman administrivia 
addresses (-owner -bounces, etc) be the FQDN, but outgoing list traffic be set 
to just the domain?

And I reset my test list to use the FQDN of the list server and it now works, 
so that’s the issue.  :-(



--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Mailman 2.1 security release

[Mark Sapiro]

On 10/20/21 11:43 AM, Mark Sapiro wrote:

On 10/19/21 6:28 PM, Mark Sapiro wrote:


Mailman 2.1.35 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/



There is an issue with my upload to gnu.org. Mailman 2.1.35 is not there 
yet. I am trying to resolve this with gnu.org. In the mean time the 
Launchpad and Sourceforge have the release.



This issue has been resolved and Mailman 2.1.35 is now available at 
https://ftp.gnu.org/gnu/mailman/ as well as the other locations.


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Moderators and admins not getting notifications of held posts

[Bruce Johnson via Mailman-Users]

On Oct 20, 2021, at 12:21 PM, Mark Sapiro 
mailto:m...@msapiro.net>> wrote:

On 10/20/21 9:46 AM, Bruce Johnson via Mailman-Users wrote:
But the emails to the moderators and admins just seems to vanish.


Is General Options -> admin_immed_notify set to Yes.

This has been set this way all along


Our MTA on the lists machine is Postfix, and it is allowed to relay to our 
actual SMTP host for general delivery. I never see the emails arrive there for 
the moderators.


What do you see? in the Postfix log? Do you see a message arriving for 
LISTNAME-owner@... and being delivered to Mailman?

Yes


What happens if you mail LISTNAME-owner@... directly?


Nothing it neither bounced or arrives.

Thinking more upon this I think this was why we originally had the email 
hostname set to the list server FQDN instead of our domain. originally mailman 
lived on our mail server, but got moved to a different system when we moved to 
Exchange for mail (and later on to O365)  We had to create weird distribution 
lists for all the lists ( ie: a DL 
t...@pharmacy.arizona.edu that has as it’s 
only member 
t...@lists.pharmacy.arizona.edu ) for 
everything to work.

This worked well for years until we moved to a new mail spam and security 
service and introduced stricter DMARC and DKIM settings for all our mail. This 
is what broke one of our larger lists (our alumni outreach list, and of course 
it’s Homecoming next week, and the last email resulted in 650+ bounces for 
DMARC failures..mostly from aol and yahoo. )

Is it possible to have the email addresses of the mailman administrivia 
addresses (-owner -bounces, etc) be the FQDN, but outgoing list traffic be set 
to just the domain?


--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Moderators and admins not getting notifications of held posts

[Mark Sapiro]

On 10/20/21 9:46 AM, Bruce Johnson via Mailman-Users wrote:


But the emails to the moderators and admins just seems to vanish.



Is General Options -> admin_immed_notify set to Yes.



Our MTA on the lists machine is Postfix, and it is allowed to relay to our 
actual SMTP host for general delivery. I never see the emails arrive there for 
the moderators.



What do you see? in the Postfix log? Do you see a message arriving for 
LISTNAME-owner@... and being delivered to Mailman?


What happens if you mail LISTNAME-owner@... directly?

Anything in Mailman's error.log?

--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Mailman 2.1 security release

[Mark Sapiro]

On 10/19/21 6:28 PM, Mark Sapiro wrote:


Mailman 2.1.35 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/



There is an issue with my upload to gnu.org. Mailman 2.1.35 is not there 
yet. I am trying to resolve this with gnu.org. In the mean time the 
Launchpad and Sourceforge have the release.



--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Moderators and admins not getting notifications of held posts

[Bruce Johnson via Mailman-Users]

We have a number of lists that are fully moderated and recently the moderators 
and admins have stopped getting notifications of held emails.

The only change that occurred prior to this was changing the hostname the list 
prefers for email, which was accomplished by changing the setting in mm_cfg.py 
and running fix_urls. List emails are going out without any issues. Thinking 
that changing the mail host would affect the aliases, I ran genaliases, then 
reloaded postfix. I have confirmed that my postfix config is correct per 
https://www.gnu.org/software/mailman/mailman-install/postfix-integration.html 

I can see the messages being sent by mailman (I have a test list I'm using to 
figure this out):

Mailman:

Oct 19 17:08:50 2021 (2708) 
 smtp to test for 1 
recips, completed in 0.005 seconds
Oct 19 17:08:50 2021 (2708) 
 smtp to test for 1 
recips, completed in 0.006 seconds


Then in the mail log (I use Postfix as an mta)

Oct 19 17:08:50 dhbmailman1 postfix/qmgr[2614]: CA3AB16111F: 
from=, size=6834, nrcpt=1 (queue active)
Oct 19 17:08:50 dhbmailman1 postfix/smtpd[6773]: disconnect from 
localhost.localdomain[::1]
Oct 19 17:08:50 dhbmailman1 postfix/smtp[6788]: C89DF160A61: 
to=, 
relay=smtp.pharmacy.arizona.edu[150.135.124.58]:25, delay=0.11, 
delays=0/0/0/0.11, dsn=2.0.0, status=sent (250 Ok: queued as E430F2320061)
Oct 19 17:08:50 dhbmailman1 postfix/qmgr[2614]: C89DF160A61: removed
Oct 19 17:08:50 dhbmailman1 postfix/smtp[6786]: CA3AB16111F: 
to=, 
relay=smtp.pharmacy.arizona.edu[150.135.124.58]:25, delay=0.14, 
delays=0/0/0/0.14, dsn=2.0.0, status=sent (250 Ok: queued as E82592B00090)
Oct 19 17:08:50 dhbmailman1 postfix/qmgr[2614]: CA3AB16111F: removed


The email to the moderated sender is recieved:

"Your mail to 'Test' with the subject

   Testing moderator messages 

Is being held until the list moderator can review it for approval.

The reason it is being held:

   Post to moderated list"


But the emails to the moderators and admins just seems to vanish.

Our MTA on the lists machine is Postfix, and it is allowed to relay to our 
actual SMTP host for general delivery. I never see the emails arrive there for 
the moderators. As I said list mails and notification emails go though just 
fine. it’s just emails to list-owner that are failing.



-- 
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/