I have put the following in /etc/mailman.cfg and restart mailman. An empty file can be created but nothing can be logged when admin or non-member subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in mailman.log and smtp.log. Thanks.
[logging.subscribe] path: subscribe.log level: debug
On 12/11/18 2:11 AM, ktso@cuhk.edu.hk wrote:
I have put the following in /etc/mailman.cfg and restart mailman. An empty file can be created but nothing can be logged when admin or non-member subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in mailman.log and smtp.log. Thanks.
[logging.subscribe] path: subscribe.log level: debug
The above is correct. As far as not seeing things in the log, very little is logged in the subscribe log. Only (un)subscription requests held for moderator approval and moderator approval of held unsubscribes but not subscribes.
In other words, unless your list's subscription police includes 'moderate' nothing will be logged in subscribe.log.
Mark Sapiro wrote:
On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote:
I have put the following in /etc/mailman.cfg and restart mailman. An empty file can be created but nothing can be logged when admin or non-member subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in mailman.log and smtp.log. Thanks.
[logging.subscribe] path: subscribe.log level: debug
The above is correct. As far as not seeing things in the log, very little is logged in the subscribe log. Only (un)subscription requests held for moderator approval and moderator approval of held unsubscribes but not subscribes.
In other words, unless your list's subscription police includes 'moderate' nothing will be logged in subscribe.log.
It looks like there is only a subscription policy but no unsubscription policy. I can't find anything even by exporting the settings using Python mailman client. Is it correct?
On 12/11/18 6:54 PM, Alan So wrote:
It looks like there is only a subscription policy but no unsubscription policy. I can't find anything even by exporting the settings using Python mailman client. Is it correct?
Mailing lists have both a subscription_policy and an unsubscription_policy, but at present only the former is exposed in REST and Postorius. You can set a list's unsubscription_policy via 'mailman shell'.
I just tested it and observe that,
- If the member send the request to list-leave@example.com, the user can confirm and the request is then moderated. The held request is also logged as expected and a notification is also sent to the owner or moderator. However, the owner cannot fulfill his/her request like those under "Subscription requests" in Postorius. The owner have to remove the address manually as a workaround.
- If the member unsubscribe through the web interface after logging into the system, the unsubscription request is processed immediately. Nothing is logged in subscribe.log. However, subscription requests are held and logged as expected if the policy is set to confirm then moderate though there is no need to confirm.
On 2/19/19 6:39 PM, Alan So wrote:
I just tested it and observe that,
- If the member send the request to list-leave@example.com, the user can confirm and the request is then moderated. The held request is also logged as expected and a notification is also sent to the owner or moderator. However, the owner cannot fulfill his/her request like those under "Subscription requests" in Postorius. The owner have to remove the address manually as a workaround.
This is now reported at https://gitlab.com/mailman/postorius/issues/332
-
Alan So -
ktso＠cuhk.edu.hk
-
Mark Sapiro