Unknown templates being used
I'm a list owner who has recently (within the last week) had my lists migrated from mailman 2 to mailman 3. The UI that we are using is Affinity. I've reviewed all of the list templates and begun to customize some of them. My issue is that I'm receiving messages that don't match any of the templates. Here is an example of one that I just received this morning. (The x's are inserted by me. The actual message provided valid addresses.)
The xxxxxxxxxx@xxxxxxxxxx.org list has 1 moderation requests waiting.
Held Subscriptions: User:xxxxxxxxxx@gmail.com
Please attend to this at your earliest convenience.
When I log in to review the request it appears to be a subscription request awaiting approval. I had previously modified the "Moderator Approval Subscription" template, which is what I would expect to have received in this circumstance. I administer several lists and have received some messages that do use the newly modified template so I assume I did it correctly. Any idea where the template for this message came from?
Thanks!
On 2/14/21 5:44 AM, Tom Stoddard wrote:
I'm a list owner who has recently (within the last week) had my lists migrated from mailman 2 to mailman 3. The UI that we are using is Affinity.
So you should be getting your support from EMWD.
I've reviewed all of the list templates and begun to customize some of them. My issue is that I'm receiving messages that don't match any of the templates. Here is an example of one that I just received this morning. (The x's are inserted by me. The actual message provided valid addresses.)
The xxxxxxxxxx@xxxxxxxxxx.org list has 1 moderation requests waiting.
Held Subscriptions: User:xxxxxxxxxx@gmail.com
Please attend to this at your earliest convenience.
That message is not built from a template. It comas from the mailman notify command which currently says
> """Creates and sends the notice to the list administrators."""
> subject = _('The {} list has {} moderation requests waiting.').format(
> mlist.fqdn_listname, count)
> # XXX This should be a template.
> text = _("""The {} list has {} moderation requests waiting.
I.e., we know it should be a template, but it currently isn't.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/14/21 1:31 PM, Mark Sapiro wrote:
On 2/14/21 5:44 AM, Tom Stoddard wrote:
I'm a list owner who has recently (within the last week) had my lists migrated from mailman 2 to mailman 3. The UI that we are using is Affinity. So you should be getting your support from EMWD.
I've reviewed all of the list templates and begun to customize some of them. My issue is that I'm receiving messages that don't match any of the templates. Here is an example of one that I just received this morning. (The x's are inserted by me. The actual message provided valid addresses.)
Thexxxxxxxxxx@xxxxxxxxxx.org list has 1 moderation requests waiting.
Held Subscriptions: User:xxxxxxxxxx@gmail.com
Please attend to this at your earliest convenience.
Yeah, the funny thing here Mark is he is not asking for support for the interface. He is wanting to know why isn't there a way for List Owners to modify moderation notices. It had nothing to do with Affinity. BTW - I told this client CLEARLY there was no template for that notification but he was welcome to join the list to ask for the source of it since I did not know.
Geez.
-- Brian Carpenter Harmonylists.com Emwd.com
On 2/14/2021 1:31 PM, Mark Sapiro wrote:
That message is not built from a template. It comas from the
mailman notifycommand which currently says> """Creates and sends the notice to the list administrators.""" > subject = _('The {} list has {} moderation requests waiting.').format( > mlist.fqdn_listname, count) > # XXX This should be a template. > text = _("""The {} list has {} moderation requests waiting.I.e., we know it should be a template, but it currently isn't.
That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used?
Are there different methods for people to use to request a subscription? Please understand that I'm new to mailman 3 and don't have knowledge of its source code. From reading some of the messages that have been sent by this list, I assume it's written in python, which is a language I have not year learned. I'm asking this because I help to administer several different lists and there are some other moderators who have very limited technical skills. I try to help them the best I can, which is why I'm trying to understand why these messages seem to differ so that I can explain it to others.
By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group.
Thank you for your time. I do recognize and appreciate the time and effort that goes into creating and maintaining open source software.
On 2/14/21 1:47 PM, Tom Stoddard wrote:
On 2/14/2021 1:31 PM, Mark Sapiro wrote:
I.e., we know it should be a template, but it currently isn't.
That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used?
The notice sent at the time the request is generated is built from a
template. The mailman notify command is intended to be run
periodically via cron set up by the site admins to send a summary of
then outstanding requests to the list admins.
You should receive the initial notice built from a template of each request as it is generated as long as the list is sent to send immediate notices.
The notice sent by mailman notify is a summary of all requests
outstanding at that time. If all the requests have been handled by the
time mailman notify is run, it won't send you anything.
Are there different methods for people to use to request a subscription?
Yes, but that's not the explanation for your question. Subscription can be requested via a web UI or via email to the list-join or list-subscribe address or via a join or subscribe command sent to the list-request address, but all methods result in the same notices to the admin.
By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group.
I agree and appreciate that Brian is very supportive. In my initial reply, it was not clear to me that Brian had referred you here which is the only reason I pointed out that he was your primary line of support.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/14/21 8:15 PM, Mark Sapiro wrote:
I agree and appreciate that Brian is very supportive. In my initial reply, it was not clear to me that Brian had referred you here which is the only reason I pointed out that he was your primary line of support.
It really didn't matter as the question by Tom was clearly related to Mailman 3 and not to Affinity.
-- Brian Carpenter Harmonylists.com Emwd.com
participants (3)
-
Brian Carpenter -
Mark Sapiro -
Tom Stoddard