Google Group works slightly differently. They "forward" emails using the
group's email address as the "From" address, not the original sender's
email address, unless the sender address happen to be a Google mail
address (including Gmail and others). Technically speaking, that's not
forwarding, but sending a new email with the original email's content,
subject, sender name (but not address), etc. information copied over.
I believe the mailing list software this mailing list is using also
supports such feature. For example, this email's "From" address is
"Bowen Song via dev <dev@cassandra.apache.org>", not my actual email
address (which is the "Cc" address). If we add the footer to all emails,
all "From" addresses, other than those Apache email addresses (e.g.
f...@apache.org), will have to be turned into "dev@cassandra.apache.org".
This works, but there's a catch. Many people (habitually) hits the
"reply all" button on their mail client instead of the "reply" button,
and as a result of that, the person being replied to will receive two
nearly identical emails, one addressed to the mailing list which is then
modified to added the footer, and the other Cc-ed to them without the
footer. This may turn out to be very annoying if a mailing list
participant can't (or doesn't know how to) setup inbox rules to filter
these out.
There's no "Prefect Solution™", unsurprisingly.
On 22/01/2024 19:08, C. Scott Andreas wrote:
Bowen and Jeremiah, thanks for remembering this.
I'd remembered the DKIM/SPF issue, but not its relationship to the
message footer - appreciate your work fixing that, Bowen.
I'm part of a few Google Groups that relay messages with an appended
footer that don't seem to encounter invalidation, but am not curious
enough to learn how they make that work right now. :)
I withdraw the proposal. 👍
– Scott
On Jan 22, 2024, at 10:56 AM, Brandon Williams <dri...@gmail.com> wrote:
That's right, I'd forgotten about this. I change my +1 to -1,
there's not enough value in this to break signatures.
Kind Regards,
Brandon
On Mon, Jan 22, 2024 at 12:42 PM Jeremiah Jordan
<jerem...@datastax.com> wrote:
Here was the thread where it was removed:
lists.apache.org
<https://lists.apache.org/thread/9wtw9m4r858xdm78krf1z74q3krc27st>
favicon.ico
<https://lists.apache.org/thread/9wtw9m4r858xdm78krf1z74q3krc27st>
On Jan 22, 2024, at 12:37 PM, J. D. Jordan
<jeremiah.jor...@gmail.com> wrote:
I think we used to have this and removed them because it was
breaking the encryption signature on messages or something which
meant they were very likely to be treated as spam?
Not saying we can’t put it back on, but it was removed for good
reasons from what I recall.
On Jan 22, 2024, at 12:19 PM, Brandon Williams
<dri...@gmail.com> wrote:
+1
Kind Regards,
Brandon
On Mon, Jan 22, 2024 at 12:10 PM C. Scott Andreas
<sc...@paradoxica.net> wrote:
Hi all,
I'd like to propose appending the following two footers to
messages sent to the user@ and dev@ lists. The proposed
postscript including line breaks is between the "XXXXX" blocks
below.
User List Footer:
XXXXX
---
Unsubscribe: Send a blank email to
user-unsubscr...@cassandra.apache.org. Do not reply to this
message.
Cassandra Community: Follow other mailing lists or join us in
Slack: https://cassandra.apache.org/_/community.html
XXXXX
Dev List Footer:
XXXXX
---
Unsubscribe: Send a blank email to
dev-unsubscr...@cassandra.apache.org. Do not reply to this
message.
Cassandra Community: Follow other mailing lists or join us in
Slack: https://cassandra.apache.org/_/community.html
XXXXX
Offering this proposal for three reasons:
– Many users are sending "Unsubscribe" messages to the full
mailing list which prompts others to wish to unsubscribe – a
negative cascade that affects the size of our user community.
– Many users don't know where to go to figure out how to
unsubscribe, especially if they'd joined many years ago.
– Nearly all mailing lists provide a one-click mechanism for
unsubscribing or built-in mail client integration to do so via
message headers. Including compact instructions on how to
leave is valuable to subscribers.
#asfinfra indicates that such footers can be appended given
project consensus and an INFRA- ticket:
https://the-asf.slack.com/archives/CBX4TSBQ8/p1705939868631079
If we reach consensus on adding a message footer, I'll file an
INFRA ticket with a link to this thread.
Thanks,
– Scott
<favicon.ico>
