List Messages Being Disrupted
To me the email at https://lists.cpunks.org/pipermail/cypherpunks/2021-April/087371.html indicates that messages are likely being disrupted somehow. To me, it does not really show whether that is happening at pglaf, an isp or government, or the behavior of the poster of the message. I have heard others (James) complain of spam bouncing on this list. I have never received a spam bounce myself. I thought Greg stated some months ago that there was no spam filter on the host. The message would be _far_ more credible if it contained an actual raw copy of the bounce email attached. But it still looks incredibly credible. The correct solution here is cryptographic message delivery. It is clear the people running this list are being harmed, that there is no easy way, already, to prove what actually happened around that spam bounce.
Hi, Karl. We do have a system-wide spam filter, but no specific filtering for the cpunks list. For example, no blacklists of who can subscribe. Any subscriber email address can post anything. Modulo that standard anti-spoofing mechanisms (mainly SPF) may cause rejection of a post if it seems to come from a spoofed email address. I also noticed that the filter generated a false positive, as you see below. This seems to be a very infrequent occurrence. I could probably figure out how to tune down the spam filter, if such "false positives" were a major distraction. It didn't bother me very much, since indeed the flagged message was rather spammy. Best regards to all, Greg (your current cpunks list maintainer) On Thu, May 06, 2021 at 06:09:58AM -0400, Karl wrote:
To me the email at https://lists.cpunks.org/pipermail/cypherpunks/2021-April/087371.html indicates that messages are likely being disrupted somehow.
To me, it does not really show whether that is happening at pglaf, an isp or government, or the behavior of the poster of the message.
I have heard others (James) complain of spam bouncing on this list. I have never received a spam bounce myself. I thought Greg stated some months ago that there was no spam filter on the host.
The message would be _far_ more credible if it contained an actual raw copy of the bounce email attached. But it still looks incredibly credible.
The correct solution here is cryptographic message delivery. It is clear the people running this list are being harmed, that there is no easy way, already, to prove what actually happened around that spam bounce.
Greg, thank you for clarifying this. Given automated marketing the measures make a lot of sense. I understand you work hard for this list. Thank you for your time and work sustaining it. I've personally had difficulty joining some lists due to listserv confirmation challenges not reaching me (most recently the hackerspaces list). An accessibility thought for future email designs.
participants (2)
-
Greg Newby
-
Karl