Slashdot Mirror


Replacing SMTP?

dousette asks: "In reading over one of the RFC's governing the SMTP protocol, and other RFC's as well, it's interesting to note that you see some big names and big companies from time to time. With all the loopholes in the current SMTP specification, is it possible for the Slashdot collective to come up with another one? Would it stand a chance in making it into a standard, or do they just listen to Cisco, AT&T, etc? I realize that a lot of people have a lot of ideas how things should be done (and they haven't been shy about posting them to Slashdot), but has anyone tried to write the RFC for a replacement protocol? As a side note (where I won't be shy about posting how things should be done), if there were a replacement trusted protocol, one could have mail received via that protocol bypass spam filtering, id checking, or whatever checks might be in place (saving processor cycles, etc). The regular checks could still be done on other mail received via the 'older' SMTP protocol. If more and more ISP's make use of this, SMTP could be gradually phased out... or if you are one for a sudden cut-over, just cut to the new one at the same time as the IPv6 upgrade!"

6 of 532 comments (clear)

  1. QWERTY speeds typing. QWERTY 4ever! by tempshill · · Score: 4, Informative

    The QWERTY-slow typewriter story has been debunked. QWERTY forever!

  2. Re:Check out Internet Mail 2000 by Angst+Badger · · Score: 4, Informative

    Maybe ISP's should charge users for each outbound SMTP connection they make? I'd happily pay 10 cents per email I sent if it would reduce the amount of SPAM I received. It would only cost me a couple of bucks a month too at the rate that I send email ...

    John Dvorak suggested a scheme along these lines, and in theory, it's a good one, though I'd suggest a tenth of a cent, which would still make sending a million emails prohibitively expensive.

    In practice, though, it's not workable. Spammers aren't using the SMTP server their ISP provides; they're using their own, just like most desktop Linux users are. As far as the ISP is concerned, Spammer X is making a bunch of outbound connections, but they're streaming out through the ISP's switches and routers, not through their SMTP server.

    To impose a tax on certain kinds of TCP connections would require detailed inspection of outbound packets. This is because a single SMTP connection can involve the transfer of many messages. To be reliable, the ISP would have to parse every outbound packet bound for port 25 on a remote system in order to count the number of emails sent. I don't think most people want that level of attention paid to their private emails.

    Moreover, this presumes that all ISPs participate honestly and thoroughly in such a system. All it would take is a few spam-friendly ISPs (and they exist, are legion, and jump around IP ranges like ferrets on a hot skillet) to render such a system useless.

    The alternative would be to implement email billing at the recipient side. Maybe AOL and Earthlink can pull that kind of blockade off, but small companies and J. Random Luser cannot.

    Bernstein's IM2000 proposal at least keeps the bandwidth consumption down, but that's primarily a cost issue for ISPs. (Don't try to convince me that if the amount of spam declined, ISPs would lower their prices.) The main hassle of spam for the user is that it takes time and energy to delete spam, and having to inspect the stuff with ambiguous could-be-from-someone-I-know subject lines would not be alleviated by IM2000; you'd still have to pick and choose what pending inbound email to read or delete.

    The fundamental problem with email as a mail system is that it's open to anyone who wants to send mail -- which is part of the point of mail in the first place -- but there is no economic limiting factor for the sender as there is with paper mail. Since we can't eliminate the openness without destroying the utility of the system, the only possible strategy is to artificially impose a cost on the sender. Unfortunately, owing to the nature of public networking, the only remotely reliable way to do that would be to route all mail through a centralized clearing house. No one company will be able to establish such a monopoly, and I don't think anyone wants the alternative -- which is to have the government do it.

    This may or may not be a soluble problem, but it is, as of today, still an unsolved problem. Personally, I think it's going to take national legislation and international agreements to stop it, and that will no doubt take a long time. Paper (actually clay tablet) mail existed for several millennia before the International Postal Union was finally established. Let's hope email is brought into line a little faster than that.

    --
    Proud member of the Weirdo-American community.
  3. SMTP AUTH by Alethes · · Score: 4, Informative
  4. Re:Costs by 680x0 · · Score: 5, Informative
    That's similar to what happens with ESMTP (yes, there already is a "new improved SMTP"). If the client understands ESMTP, it sends a new command to begin the conversation ("EHLO" instead of the older "HELO"). If the server is old, SMTP-only, it sends an error message, and the client tries again with plain old SMTP. If the server does do ESMTP, it sends a reply, along with the list of ESMTP goodies it understands. Some of the goodies are sending msg size ahead of time (so the server can reject the message due to size limitations before the whole message gets transferred), delivery status notification, and so on. None of the current "capabilities" really help filter out spam, but if you come up with a new feature, you can add it as an ESMTP capability, and whenever both client and server support it, it will be used.

    Check out RF2821.

  5. Re:... at the same time as the IPv6 upgrade! ??? by darrylo · · Score: 5, Informative
    After all, it's now past the death of typewriters, and we're still using the typewriter keyboard from nearly two centuries ago. And we use a ridiculous rail gauge, because the standard was set centuries ago.

    Don't laugh. The following might be apocryphal, but it's still interesting .... I don't know where it comes from, though:

    The US standard railroad gauge (width between the two rails) is 4 feet, 8.5 inches. That's an exceedingly odd number. Why was that gauge used?

    Because that's the way they built them in England, and the US railroads were built by English expatriates.

    Why did the English build them like that? Because the first rail lines were built by the same people who built the pre railroad tramways, and that's the gauge they used.

    Why did "they" use that gauge then? Because the people who built the tramways used the same jigs and tools that they used for building wagons which used that wheel spacing.

    Okay! Why did the wagons have that particular odd wheel spacing? Well, if they tried to use any other spacing, the wagon wheels would break on some of the old, long distance roads in England, because that's the spacing of the wheel ruts.

    So who built those old rutted roads? The first long distance roads in Europe (and England) were built by Imperial Rome for their legions. The roads have been used ever since.

    And the ruts in the roads? Roman war chariots first formed the initial ruts, which everyone else had to match for fear of destroying their wagon wheels. Since the chariots were made for (or by) Imperial Rome, they were all alike in the matter of wheel spacing.

    The United States standard railroad gauge of 4 feet, 8.5 inches derives from the original specification for an Imperial Roman war chariot.

    Specifications and bureaucracies live forever. So the next time you are handed a specification and wonder what horse's ass came up with it, you may be exactly right, because the Imperial Roman war chariots were made just wide enough to accommodate the back ends of two war horses. Thus, we have the answer to the original question.

    When we see a Space Shuttle sitting on its launch pad, there are two big booster rockets attached to the sides of the main fuel tank. These are solid rocket boosters, or SRBs. The SRBs are made by Thiokol at their factory in Utah. The engineers who designed the SRBs might have preferred to make them a bit fatter, but the SRBs had to be shipped by train from the factory to the launch site.

    The railroad line from the factory had to run through a tunnel in the mountains. The SRBs had to fit through that tunnel. The tunnel is slightly wider than the railroad track, and the railroad track is about as wide as two horses' behinds.

    So, the major design feature of what is arguably the world's most advanced transportation system was determined over two thousand years ago by the width of a horse's ass!

  6. Re:... at the same time as the IPv6 upgrade! ??? by jc42 · · Score: 4, Informative

    You'll find some good commentary on this particular bit of mythology at:

    http://www.snopes.com/history/american/gauge.htm

    Their best comment on it is probably:

    Marvelling that the width of modern roadways is similar to the width of ancient roadways is sort of like getting excited over a notion such as "modern clothes sizes are based upon standards developed by medieval tailors." Well, duh.

    Then they go into a rather detailed explanation of why it's basically an uninteresting historical semi-truth for exactly this sort of reason.

    Still, the modern "standard" railway gauge does go back at least a few centuries. And the early railroad equipment was derived from the sort of horse-drawn vehicles (carriages and carts), so of course it was about the same size.

    But in the "standards" sense, the current American rail gauge doesn't really trace back to anything Roman, or much before around 1800. Before that, it's just vague copying, with sizes coming out nearly the same because the job (carrying people and their luggage) was about the same.

    The Space Shuttle tie-in is completely bogus.

    --
    Those who do study history are doomed to stand helplessly by while everyone else repeats it.