On 2/14/22 1:18 PM, joea- lists wrote:
The reason has to do with "reply" and "reply to all" with the email client/system I am using and prefer to continue using for now.
To each their own.
Being subscribed to several lists, I find some variation between them regarding the headers they provide and how my "reply" feature works.
I've noticed similar.
Those that provide "Reply-to: somelist" act as expected and place the list address in the To: field. Those that do not (users@spamassassin.apache.org included) find the address of the poster rather than the list in the To: field.
Ya.
While this is not a new issue, I do occasionally fail to correct the address issue and an email goes astray. '
Been there. Done that.
I'm aware that "modern" clients can deal with this and there are more "practical" solutions, but I view this as an opportunity for "exercise" and perverse amusement.
I understand /why/ you might think that.
Does not appear to be something that can or should be done in SA, just exploring possible avenues, or, abandoning the idea completely.
However, I believe what you are wanting to do is outside of SpamAssassin's (et al.) preview. Rather I think this is better done with something like procmail + formail. SpamAssassin tends to be system wide while procmail + formail tends to be per-user. And I suspect that what you're wanting to do definitely falls under the per-user end of that category.
I have implemented some procmail + formail rules to do very similar to what you are wanting to do. One big difference is that I /usually/ *add* a List-Post: header and leverage my MUA's Reply to List functionality. That way I am able to do a normal reply or reply to all and have the message go where the original author and / or mailing list administrator intended for it to go. I say usually because I do use the same procmail + formail functionality to alter additional things in some very specific situations. But all of this only applies to my user and definitely not system wide.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
