Don’t think logically, think like a narcissist: If you plant that bug, you exactly know
how to fix it. The more damage it causes, the higher the admiration if you fix it. HOWEVER, for that to work you'd need to blame someone else and gaslight everyone into believing your story. That makes it a tad more difficult, but I think it’s still doable.
Thanks. IDK it's first time for me getting attention and users in a thing I built for my self but I feels like that users liked the features and the usability
If I were good at financial math (which I'm not), I would calculate that against a regular loan. E.g., how high would the interest be, if you were to keep the device.
The shortwave WWV, not so much, except to check if your shortwave radio is working. Canada's shortwave CHU was shut down last month.
The 60 kHz WWVB, yes. Plenty of cheap wall clocks have "atomic time" as it is marketed over here, meaning it has a radio receiver. You can pick one up at the grocery store. It depends on where you live if it actually works though. Where I live it works pretty well, but I've heard it does not work so well if you live on the east coast. That's quite a ways from Colorado.
I think both WWV and WWVB were on the chopping block a few years ago, because the government decided it wasn't worth the $100,000 per year to keep them running. Thankfully that decision was overturned.
Greylisting is not perfect, not even close, but it allows servers to reject huge amounts of garbage mail while allowing new mail from unexpected parties without user intervention.
It is similar but not the same thing. It does not have anything to do with the email being legit (non spam) or not. It only catches emails that do not do what they supposed to do when they are deferred for a little bit. They are supposed to try again later. (A super nice feature of email which protects you from losing all incoming emails when your server is down for a short time). The reasoning here is hopefully a spam script or software will not implement the standard properly or will skip apparently broken destinations.
What parent wants is also possible and I remember people doing it as far back as the early 2000s. You would basically manually whitelist an email or have them bypass the list (once or always) with something like a key word or token sort of like a captcha which can be shared off band.
"We" tried this in the late 1990s. I remember writing an exim config to do this a couple of ways back in my ISP times:
1. "The recipient will not get this message until you authenticate yourself as a legitimate sender at this URL [...]" - resulted in people never getting mail from no-reply addresses they cared about (banks, e-com, etc.)
2. "This sender has sent you an email, with this subject and this first paragraph. Click here to whitelist, here to blacklist" - created a lot of churn on first setup that users didn't like as a UX
Baking it into the protocol - even now in SMTP and IMAP land - is doable, but would be resisted by email providers who, for example, make their money selling data to marketing agencies. Like, you know, Google, Microsoft, Yahoo...
I've seen other approaches proposed - even at IETF level - over the years, including digital postage stamps (sender pays to send email, your server gets paid, and may reject non-stamped/paying email), but it's the usual network effect: until it becomes widely supported it won't "stick". The stuff that has been adopted has basically been stuff that Google likes, period.
It also misses one of the biggest fundamental problems with SMTP: Lack of per-recipient replies. Though you could potentially mandate a single recipient per request. We wrote a plugin to emulate that in Haraka, where you just 400 (temp fail) each subsequent recipient. The downside is some sources just plain don't retry.
LMTP is a small modification of SMTP with a per-recipient response code - but I'm not sure what it's intended for. It isn't used on the internet. It's sometimes used as IPC within a mail server.
LMTP is for delivering to an IMAP (or JMAP) mailbox, generally. We also have a plugin for that. But it has certain flaws for exposing it to the internet (I just forget what they are right now).
There's no such thing as an IMAP mailbox. Mail receiving is split down the middle. Your SMTP server stores the email in a folder and your IMAP server provides access to that folder.
For context, I'm the author of Haraka, a popular open source SMTP server.
SMTP servers don't necessarily store anything. They have two responsibilities: Receiving and delivering email. What they do with the emails they receive is up to the configuration.
Baking any of these into the protocol will invalidate it. If there was a standard way to specify a URL to open to whitelist an address, spammers would just whitelist their addresses.
They are quite handy, though. Also, there is a (commercial, proprietary) weather protocol encoded on top. However, since the end of june, there are technical issues and no forecast is being transmitted. [1]
reply