Path: csiph.com!usenet.pasdenom.info!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!217.73.144.45.MISMATCH!feeder2.ecngs.de!ecngs!feeder.ecngs.de!81.171.118.61.MISMATCH!peer01.fr7!news.highwinds-media.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.php Subject: Technical requiremenets for Usenet messages (was: Re: response for server every second) Date: Fri, 26 Jun 2015 10:43:04 +0200 Lines: 50 Message-ID: <558D1098.50103@arnowelzel.de> References: <94be00e7-99d7-4d84-97a5-538535a0317d@googlegroups.com> <55784c9c$0$2956$e4fe514c@news2.news.xs4all.nl> <10793488.AfY9kfu9Qn@PointedEars.de> <5589770f$0$2889$e4fe514c@news2.news.xs4all.nl> <15774402.MeXr0uTVEA@PointedEars.de> <1543927.4VZE17etc1@PointedEars.de> <558C1BCC.7030706@arnowelzel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: individual.net v7PqtW7WBhaJioX7uBFKww4W7FR0X2y4JNyy3WLHEFr4GQwwfU Cancel-Lock: sha1:wfyEPcb1h8d3GMtjE1J2IlM7X/M= X-Enigmail-Draft-Status: N1110 In-Reply-To: X-Received-Bytes: 2702 X-Received-Body-CRC: 2925140113 Xref: csiph.com comp.lang.php:15533 Am 2015-06-26 um 02:31 schrieb Jerry Stuckle: [...] > Sorry, sucker - it is not required you have a valid email address - only > one which can be easily decoded. See : 2.1. Required Header lines 2.1.1. From The "From" line contains the electronic mailing address of the person who sent the message, in the Internet syntax. It may optionally also contain the full name of the person, in parentheses, after the electronic address. [...] I don't see anything like "does not need to be the valid address, as long as humans can decode it somehow manually". Also the draft for the son of RFC1036 does not contain anything like this - see : "The From header contains the electronic address, and possibly the full name, of the article's author [...] The address SHOULD be a valid and complete Internet domain address, capable of being successfully mailed to by an Internet host [...]" Again no word about "may be invalid as long as a human is able to decode it somehow". But I know what will follow now: You will explain that RFC1036 is quite old, the draft is also really old and they do not fit current needs and therefore are not valid any longer. Of course you would never write your own RFC draft to straighten this out - because RFCs asking for a valid e-mail address or to keep signatures within reasonable limits are for pedantic trolls - aren't they? -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de