RFCs and spam
Oct. 18th, 2006 12:54 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
miriam_eI mentioned a little while ago how I realised that there was an extremely easy way to stop pretty-much all spam. I found it hard to believe that I was the only one to come up with such an idea so I started looking into it. I'm extremely surprised to find that we should really be getting almost no spam at all. The major reason spam continues to swamp the network is that most mail servers don't actually implement the existing standards and everybody basically says "oh it's too hard" when really, it isn't.
I have first-hand experience at giving in to this. For many years I used Eudora for my email. A few years ago I found a lot of emails suddenly weren't getting through to me. At first I thought it was a bug in the latest version of Eudora, but eventually I realised Eudora was doing the right thing. It didn't recognise broken emails. In almost all cases those broken, invisible emails came from people using Microsoft Office to send emails. Amazing!
I tried and tried to get people to use a safe and standards-compliant email program, but I might as well have been talking to trees. In the end I had to drop Eudora because I couldn't afford to lose work. Mozilla is more lax, and I now get all those emails, but that isn't necessarily a good thing. I am seriously considering going back to Eudora. If people want to use broken shit then maybe I just shouldn't see it. The trouble is, of course, most people don't realise how seriously flawed Microsoft products often are. They are encouraged to think that they're some kind of standard.
I still get people sending me Microsoft Word and Microsoft PowerPoint documents as if they were standards. Aaaarrrgh! I and many other people don't own or want Microsoft Word or PowerPoint. They are costly, dangerous, bloated, anti-standards programs.
[end rant]
RFCs
Incidentally, in my reading about email standards I've been referring to the original RFC documents (Request For Comments) that are the discussion papers that most of the standards grow out of. I noticed that the very early ones are now up there too. http://www.faqs.org/rfcs/rfc-index.html For some time many of the early ones were missing.
The very first one rfc1 is there. It talks about packets (called messages) with a header containing a 5-bit destination. That means it could be sent to one of up to 32 possible destinations. hehehehehe :) Somehow I suspect the awsome future of the internet had not hit them yet.
I have first-hand experience at giving in to this. For many years I used Eudora for my email. A few years ago I found a lot of emails suddenly weren't getting through to me. At first I thought it was a bug in the latest version of Eudora, but eventually I realised Eudora was doing the right thing. It didn't recognise broken emails. In almost all cases those broken, invisible emails came from people using Microsoft Office to send emails. Amazing!
I tried and tried to get people to use a safe and standards-compliant email program, but I might as well have been talking to trees. In the end I had to drop Eudora because I couldn't afford to lose work. Mozilla is more lax, and I now get all those emails, but that isn't necessarily a good thing. I am seriously considering going back to Eudora. If people want to use broken shit then maybe I just shouldn't see it. The trouble is, of course, most people don't realise how seriously flawed Microsoft products often are. They are encouraged to think that they're some kind of standard.
I still get people sending me Microsoft Word and Microsoft PowerPoint documents as if they were standards. Aaaarrrgh! I and many other people don't own or want Microsoft Word or PowerPoint. They are costly, dangerous, bloated, anti-standards programs.
[end rant]
RFCs
Incidentally, in my reading about email standards I've been referring to the original RFC documents (Request For Comments) that are the discussion papers that most of the standards grow out of. I noticed that the very early ones are now up there too. http://www.faqs.org/rfcs/rfc-index.html For some time many of the early ones were missing.
The very first one rfc1 is there. It talks about packets (called messages) with a header containing a 5-bit destination. That means it could be sent to one of up to 32 possible destinations. hehehehehe :) Somehow I suspect the awsome future of the internet had not hit them yet.