Hallo Bernd, * Bernd Schmelter [23.07.02 20:48]:
hmmm, das lese ich anders.
http://www.rfc-editor.org/rfc/rfc2822.txt
Allerdings ist die M.-ID optional, aber wenn, dann eindeutig. Von fqdn steht da nix, wird aber imho gerne genommen wegen "eindeutig".
Die M-ID von Evolution sollte demnach nicht falsch sein.(?)
In rfc1036 habe ich folgendes gefunden: ,----[ rfc1036 ]- | | 2.1.5. Message-ID | | The "Message-ID" line gives the message a unique identifier. The | Message-ID may not be reused during the lifetime of any previous | message with the same Message-ID. (It is recommended that no | Message-ID be reused for at least two years.) Message-ID's have the | syntax: | | <string not containing blank or ">"> | | In order to conform to RFC-822, the Message-ID must have the format: | | <unique@full_domain_name> | | where full_domain_name is the full name of the host at which the | message entered the network, including a domain that host is in, and | unique is any string of printing ASCII characters, not including "<" | (left angle bracket), ">" (right angle bracket), or "@" (at sign). | `---- Gruss, Andreas -- " Schlechte Zeugen sind Augen und Ohren fuer Menschen, wenn sie Barbarenseelen haben " [Heraklit]