A bit off topic, but I'll bite. How did you come to that conclusion? With which specific products/services are you concerned? What are your preferred email service providers (and why)?

BDD formed many of his opinions over 65 million years ago, before the Cretaceous–Paleogene extinction event, so please keep that in mind before you engage in any debates with him. I don't try to argue with him, but I have been known to tease him from a safe distance, always being mindful of that dangerous tail of his.

_________________
Got a kilobyte lying fallow in your 65xx's memory map? Sprinkle some VTL02C on it and see how it grows on you!

Mike B. (about me) (learning how to github)

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

From the perspective of the general forum user, these tactics and observations aren't going to make any difference.

It's handy, BDD, that you have your own server and can see the raw incoming email. In particular, you're in the position to see and report on the envelope and the transport. Whereas in general, those of us using email providers might see only the header and the body.

rehsd, it will be interesting to see if you can tweak your setup to improve matters. It might possibly help Mike figure out an improvement.

The issue appears to be outside of the M365 email services to which I subscribe. I have essentially disabled all incoming security/SPAM checks for 6502.org, by domain name, from email address, and SMTP source IP (i.e., the sending server, listed earlier in the thread). Prior to even doing this, the incoming logs should have shown any dropped emails. I checked again today, and the logs are empty for anything related to this forum.

If someone could PM me (or post here) the full header of a 6502.org forum email notification, that would be helpful. (something like looks like this)

As another data point, my notifications also get delivered to the Spam folder in Gmail.

_________________
BB816 Computer YouTube series

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Nothing in the header stood out to me that would prevent delivery.

If someone from the 6502.org email side of things (Mike?) wants to dig deeper into it, we could do a quick telnet test from the 6502.org sending server.

I'll just plan on manually checking the forum periodically.

Just to note: today I got a notification email direct to my inbox. With luck, the overactive antispam measures will no longer get in the way.

Edit: just got four delivered into spam, so we're not out of the woods yet.

I noticed your message on Reddit which might cause some people to think that the 6502 Forum is snooty or elitist when this is not the case.

Since the 1990s, Bill Gates has wanted to charge a "digital stamp" for sending email. This hasn't happened because people are collectively cheap-skates. However, services cost money to run and there is a Big Tech mantra that "If you're not paying for the service, you're the product." This has led to a double-dipping scheme where The Product receives adverts while bulk email senders are expected to pay fees for delivery. My information might be highly out-dated but believe that 800-1000 messages per month were allowed. Anything more can be overcome by waving some greenbacks. Don't have any money? That's your problem. It is very much like dealing with customs. You probably won't get charged for five PCBs but if you spend USD1000, your order will be blocked until you pay taxes.

6502 Forum membership has grown by 1/5 since I joined and many people set notification flags on dormant topics. Therefore, I presume that we've hit a plausible threshold of 1000 messages per month. Sheep20, who knows more than me about email, recommended batching notification messages to indefinitely defer this problem.



Yahoo has a higher threshold. That is why it is currently unaffected. However, sooner or later, every major email service will want a cut.



If you receive adverts then you're being triple-dipped. Either way, you're being treated like the product. That's disrespectful.

_________________
Modules | Processors | Boards | Boxes | Beep, Beep! I'm a sheep!

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

As much as I hate to say it, while this statement was true before 2000, maybe 2010, hosting your own email has become exponentially difficult to do in the past decade if you want reliable delivery to the major players (Gmail...). Having a basic setup is easy, but if you want your sent messages to land outside the Spam box in Gmail, that's another story, as evidenced by the existence of this thread. Keeping up with the various metadata requirements, making sure the server doesn't end up on a blacklist, making sure to progressively warm-up an IP by increasing email traffic over time, etc... are time investments that few people are ready to make.

_________________
BB816 Computer YouTube series

A lot of people aren't going to have a way to host an email server on-prem and will need to rent a cloud server of some sort, because blocking incoming port 25 to residential customers is a common way to cut down on open relays running on hijacked computers. For someone paying for a service now maybe that's not a big deal, but for people used to free email it may be a deal breaker.

The other aspect to consider is maintenance. Once you've got a mail server on the net you're gonna need to keep up on your security patches and monitoring for intrusion attempts. Sure you can turn on auto-updates and you'll probably be fine...until you're not.

Here's a simple example. I currently run two cloud-hosted servers for myself, one for Minecraft for me and the wife, and one that runs my blog and an email server. The email server is solely for the use of a friend of mine whose domain I have hosted for nearly 25 years, going way back to when I ran an ISP. About two months ago he hits me up on FB and says "hey I'm not getting email". So, I go poke around...I see email coming in, and I see it delivering to his inbox. But he's not seeing it. After much digging it turns out somebody decided to deprecate some older TLS certs that were being used by the IMAP server, so his client wasn't actually logging in.

Anyway, my point is, while it's not hard to set up an email server, it does take some elbow grease (and either existing knowledge, or good Google-fu) to maintain it. Not everyone has the skills and/or time to do that, and that's fine.

That being said I understand your sentiments. I've been on Gmail almost since it opened, and I'm more entrenched in the Google ecosystem than I care to admit. Ever since the death of free Workspace accounts though I've been mulling over hosting my own email again; I've got the server space after all. I am just not yet sure if I want the added responsibility in my life right now.

BTW I' not surprised you like sendmail. The config file looks like old school line noise.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

And it can be even worse; I forgot to mention that it's also common practice to blacklist incoming mail from IP blocks that are known to be assigned to residential cable and DSL customers. So even if you just try to do outgoing mail directly from home you may find that those emails are silently thrown into a black hole.