Hi,

I think it will be a good feature to have. Thinking about it's implementation however assumes that every mail clients uses the thread view mail option. Also those who subscribe in the middle of a conversion will most likely not get the footer.

Nerveless it's good to have it for use according to our environment.

Cheers!

Sent from my Asus Zenfone2 Kindly excuse brevity and typos. On 27 Aug 2015 18:50, "Billy Crook" <billycrook@gmail.com> wrote:

I've noticed that as people reply to threads on my mailman instance, I see copies of the footer pile up at the bottom of each message.

Rants about top/inline/bottom posting aside, I thought it would be a smart feature of mailman to look for a copy of the footer in any incoming message before adding the footer to the bottom.

Or perhaps easier to implement, instead of "apply a footer" or "don't apply a footer", add the option "apply footer to the first message of each thread and no other messages of the same thread"

Am I just missing where this setting is, or has this not been thought of yet.

"apply footer only if footer text not already in message" would be my logic of preference.

If that's not already something mailman can do, where would I modify the code to add it?

Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/seun.ojedeji%40gmail.c...

You may be interested in this thread: https://mail.python.org/pipermail/mailman-users/2012-April/073181.html

Laura

Billy Crook writes:

Am I just missing where this setting is, or has this not been thought of yet.

It's been thought of, and it's just plain hard to do, because automatically editing mail bodies robustly is just plain hard to do.

If you have a vast majority of users who use the same MUA, you can probably get away with assuming that MUA's format, and will rarely, if ever, get complaints from users whose mail has been mutilated. Given the variety and generally abysmal level of standard conformance of the MUAs out there, we can't count on that. :-(

"apply footer only if footer text not already in message" would be my logic of preference.

If there is any personalization (eg, user-specific unsubscribe link), this logic doesn't work. You need to remove the existing footer(s) for other user(s), and add the correct one. If you're not using any personalization, this isn't a problem, of course.

It's also ugly, as in most cases the replying user's MUA will quote the footer, often multiple times.

The "first in thread" logic has the same problems of personalization and ugliness.

If that's not already something mailman can do, where would I modify the code to add it?

Mailman/Handlers/Decorate.py. Warning: Mailman 2 doesn't know anything about threads, and Mailman 3 (unmerged development code) has a rather different idea of threads (called "dynamic lists", "dlists" for short). So you'll have to use the "detect existing footer" logic, not the "first in thread" logic.

Hi,

I think it will be a good feature to have. Thinking about it's implementation however assumes that every mail clients uses the thread view mail option. Also those who subscribe in the middle of a conversion will most likely not get the footer.

Nerveless it's good to have it for use according to our environment.

Cheers!

Sent from my Asus Zenfone2 Kindly excuse brevity and typos. On 27 Aug 2015 18:50, "Billy Crook" <billycrook@gmail.com> wrote:

I've noticed that as people reply to threads on my mailman instance, I see copies of the footer pile up at the bottom of each message.

Rants about top/inline/bottom posting aside, I thought it would be a smart feature of mailman to look for a copy of the footer in any incoming message before adding the footer to the bottom.

Or perhaps easier to implement, instead of "apply a footer" or "don't apply a footer", add the option "apply footer to the first message of each thread and no other messages of the same thread"

Am I just missing where this setting is, or has this not been thought of yet.

"apply footer only if footer text not already in message" would be my logic of preference.

If that's not already something mailman can do, where would I modify the code to add it?

Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/seun.ojedeji%40gmail.c...

You may be interested in this thread: https://mail.python.org/pipermail/mailman-users/2012-April/073181.html

Laura

Billy Crook writes:

Am I just missing where this setting is, or has this not been thought of yet.

It's been thought of, and it's just plain hard to do, because automatically editing mail bodies robustly is just plain hard to do.

If you have a vast majority of users who use the same MUA, you can probably get away with assuming that MUA's format, and will rarely, if ever, get complaints from users whose mail has been mutilated. Given the variety and generally abysmal level of standard conformance of the MUAs out there, we can't count on that. :-(

"apply footer only if footer text not already in message" would be my logic of preference.

If there is any personalization (eg, user-specific unsubscribe link), this logic doesn't work. You need to remove the existing footer(s) for other user(s), and add the correct one. If you're not using any personalization, this isn't a problem, of course.

It's also ugly, as in most cases the replying user's MUA will quote the footer, often multiple times.

The "first in thread" logic has the same problems of personalization and ugliness.

If that's not already something mailman can do, where would I modify the code to add it?

Mailman/Handlers/Decorate.py. Warning: Mailman 2 doesn't know anything about threads, and Mailman 3 (unmerged development code) has a rather different idea of threads (called "dynamic lists", "dlists" for short). So you'll have to use the "detect existing footer" logic, not the "first in thread" logic.