From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] An Amtrak trip through the real world yesterday
Date: Fri, 27 Oct 2023 14:18:27 -0700 [thread overview]
Message-ID: <eccb75039957cb22ef09f27fa2390900@rjmcmahon.com> (raw)
In-Reply-To: <8f7e749d-d6d1-4803-af6f-58c3b6acb469@3kitty.org>
I received Nathan's email through my personal server & MTA.
I've been running my own MTA since 2000. It's a non trivial amount of
work to keep it useful & working. Many list providers went out of
business likely because the cost to run them exceeded revenues.
The majors read everyone's email via ML. One may need to get through may
be to make sure the content of an email will trigger a high value
targeted ad so the email has monetary value for the "free" email service
provider. We get what we get when somebody else actually pays our bills.
Every email sent is a customer match opportunity which suggests the
incentives are less on source side pays and more on source side triggers
ads.
Bob
> On 10/27/23 12:37, Dave Taht via Nnagain wrote:
>
>> I could get mad that I figure 80% of this new email list is
>> vanishing into spam boxes. As the administrator, I check my logs,
>> the email was accepted, it is not in any public spam blockers like
>> RBL, and I have no idea what to do or who to contact or what
>> algorithm to bypass to make sure the mail gets through.
>
> I've never understood how spam filters operate. As an end-user, it
> does seem to me that email has been getting less reliable over the
> decades.
>
> I've digitally signed this message. Perhaps that helps get through
> the filters? Can nnagain@lists.bufferbloat.net sign its messages? I
> realize email signing is likely imperfect for hardcore security needs.
> Why don't more people sign their email?
>
> Jack Haverty
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
next prev parent reply other threads:[~2023-10-27 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 19:37 Dave Taht
2023-10-27 19:58 ` Jack Haverty
2023-10-27 21:18 ` rjmcmahon [this message]
2023-10-27 21:48 ` [NNagain] Spam filtering Hal Murray
2023-10-27 23:23 ` Nathan Simington
2023-10-27 23:45 ` Dave Taht
2023-10-28 10:50 ` Frantisek Borsik
2025-04-06 1:21 ` Daniel Ezell
2025-04-06 10:23 ` Frantisek Borsik
2025-04-06 14:22 ` Tanya Weiman
2025-04-06 18:11 ` Frantisek Borsik
2023-10-28 16:55 ` rjmcmahon
2023-10-28 10:04 ` [NNagain] An Amtrak trip through the real world yesterday Frantisek Borsik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eccb75039957cb22ef09f27fa2390900@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox