Stephen Morris: > > > If the issue is that the echoing of the sent mail to the sent folder on > > > the server is causing gmail to think it doesn't need to retain the > > > "echo", if I configure Thunderbird to save the sent mail in a local > > > "sent" folder, would that rectify the issue for both replies and sent > > > mail?
Tim: > > That sounds like it'd work, to me. Stephen Morris > It looks like changing the sent location to a local folder makes no > difference either. So, probably an issue of your address being the poster, rather than it already having a copy of the message (going by duplicate message IDs). Many systems, now, do a check for mail that is authorised. In other words, when you post from a certain domain name, that domain has records showing the services allowed to post its mail. When you post to someone using your gmail address, the recipient's service checks that the server sending it is an authorised sender for that address. And if it isn't, then it can flag it as spam, or refuse to accept it (as two common courses of action). This list server can do that, and accepts your post (as gmail was authorised to handle your gmail address). When it relays your post to all the recipients, their servers can do a similar check, and test if the server that sent the message is authorised to do so. The list server will NOT be an authorised poster of gmail addresses, and various servers (gmail included) may do whatever they automatically do with spam. The list server will only be an authorised poster of messages coming from its own addresses. *This* kind of spam (messages sent through unauthorised servers) is treated far more harshly than messages that seem like spam because the content has used a few bad keywords or come from various untrustworthy sources (all of which often just end up in your junk folder). The common solution to this issue is that list servers will rewrite the addresses in the mail before forwarding it. Replacing your from address with their own, which they will be an authorised poster for it. And possibly adding your address in another header so people could reply privately to you if necessary. However, I received your mail through the server with it coming "from" your gmail address. There's every chance that some of the list headers give leeway to this issue, to my servers. But perhaps gmail is being more pernickity about this, and blocking your reception. I don't use gmail as a rule. I have a gmail address, it's used by a few things (mostly the various android things that require one for their authentication purposes), but it's rare that I make posts through it. It's such a pain in so many ways. Many years ago I set up a yahoo address since yahoo was responsible for a lot of the spam I received back then, I figured they deserved to have to deal with it. There are a variety of free email services that you could use instead of gmail, but the "authorised sender" check is becoming a much more wide-spread thing. I think list servers are going to have to modify their behaviour more. Probably having to change *every* poster's "from" address to say the post came from the list (as it does to my yahoo address), not just the ones they've already discovered to be problematic. If a list admin had options for doing that kind of thing to individuals (whether or not rewriting their "from" address is enabled), perhaps that was what they did for you beforehand. When lists do that rewriting the address kind of thing, you can simply include your personal address in a footer if you want to be able to receive direct replies. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 (yes, this is the output from uname for this PC when I posted) Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
