Re: [FAQ] Ungueltige eMail-Adressen im Usenet <2005-01-17>



Florian Finkenzeller wrote:

> 3.1 Verstoße ich damit nicht gegen technische Standards?
>
> Eine ungültige eMail-Adresse im From eines Usenet-Postings verstößt
> gegen RFC 850 und RFC 1036, in denen die Grundlagen des heutigen
> NNTP-Protokolls dargestellt werden. Die entscheidende Textstelle aus
> RFC 850 lautet:
>
> 2.1.3 From The From line contains the electronic mailing
> address of the person who sent the message, in the ARPA
> internet syntax. It may optionally also contain the full
> name of the person, in parentheses, after the electronic
> address. The electronic address is the same as the entity
> responsible for originating the article, unless the Sender
> header is present, in which case the From header might not
> be verified.
>
> Interessant ist dabei vor allem die Tatsache, dass der Autor des
> Textes offensichtlich davon ausging, dass der Absender eines Postings
> nur eine einzige eMail-Adresse haben würde.

Das steht da mit keinem Wort. Ginge man davon aus, stünde da "the only".

> 1983, als RFC 850 verfasst wurde, traf dies in der Regel auch noch
> zu. Bereits an diesem kleinen Faktor lässt sich jedoch bereits der
> Hauptkritikpunkt an dem 20 Jahre alten Dokument festmachen: Es
> geht von Voraussetzungen aus, die in der jetzigen Zeit schlicht
> unzutreffend sind. Insbesondere existierte in der Frühzeit des
> Usenet das Spam-Problem noch nicht.

Folgefehler.


RFC850 ist durch RFC1036 obsolete, ersteres als Referenz zu benutzen ist
folglich unzulässig:

| STATUS OF THIS MEMO
|
| This document defines the standard format for the interchange of
| network News messages among USENET hosts. It updates and replaces
| RFC-850, reflecting version B2.11 of the News program.

(Dies kann man auch bei http://www.rfc-editor.org/ nachlesen.)

In RFC1036 steht:

| 2.1.1. From
|
| The "From" line contains the electronic mailing address of the
| person who sent the message, in the Internet syntax. [...]

Damit bezieht es sich auf RFC822, obsoleted durch RFC2822 (vom
April 2001, als das Spam-Problem bereits existierte), in dem steht:

| 3.4. Address Specification
|
| A mailbox receives mail. [...]

RFC2822 ist im Standards Track:

| Network Working Group P. Resnick, Editor
| Request for Comments: 2822 QUALCOMM Incorporated
| Obsoletes: 822 April 2001
| Category: Standards Track

Das bedeutet lt. RFC2026:

| 4. THE INTERNET STANDARDS TRACK
|
| Specifications that are intended to become Internet Standards evolve
| through a set of maturity levels known as the "standards track".
| These maturity levels -- "Proposed Standard", "Draft Standard",
| and "Standard" -- are defined and discussed in section 4.1.

Sucht man bei http://www.rfc-editor.org/ nach RFC2822, stellt
man fest (Tabelle der Lesbarkeit halber transformiert):

Number: RFC2822
Title: Internet Message Format
Author or Ed.: P. Resnick, Ed.
Date: April 2001
Format: ASCII
More Info (Obs&Upd): Obsoletes RFC822
Status: PROPOSED STANDARD
^^^^^^^^^^^^^^^^^
Das bedeutet nach RFC2026, Abschnitt 4.1:

| [...]
| A Proposed Standard specification is generally stable, has resolved
| known design choices, is believed to be well-understood, has received
| significant community review, and appears to enjoy enough community
| interest to be considered valuable. However, further experience
| might result in a change or even retraction of the specification
| before it advances.
| [...]


PointedEars
.



Relevant Pages

  • Re: weird scans from port 80
    ... So nmap doesn't have an OS-detection routine for any sort of reason ... > For gods sake would you rather have had the entire RFC posted? ... > insisting on violating the standards in the holy name of the firewall. ...
    (comp.os.linux.security)
  • Re: Perl DBI Module: SQL query where there is space in field name
    ... Well, there is this slight problem of standards, encoded into RFCs. ... The relevant RFC in this case would be RFC 2046. ... serious newsreader does not render ... standard for usenet. ...
    (comp.lang.perl.misc)
  • Fwd: [ntpwg] RFC 5907 on Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)
    ... A new Request for Comments is now available in online RFC libraries. ... of such a network participant and it is part of the NTP version 4 ... This document is a product of the Network Time Protocol Working Group of ... STANDARDS TRACK: This document specifies an Internet standards track ...
    (comp.protocols.time.ntp)
  • Re: OT Mo Dowd Alert! Attn Slip Kid...
    ... and then pass a tougher law ... So, we toss out our standards, so we can impose our ... People used to die for freedom...wot, ... Because it's not a question of how well you play, ...
    (rec.music.beatles)
  • Re: Is an ARP Flooding possible?
    ... though a lot more are drafts of standards ... 2026 The Internet Standards Process -- Revision 3. ... BCP0009) (Status: BEST CURRENT PRACTICE) ... 1871 Addendum to RFC 1602 -- Variance Procedure. ...
    (comp.os.linux.networking)