Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
wow, RFC-82 was pretty exciting. history in the making. i had never seen it before. http://www.globecom.net/ietf/stdindex.php is a new favorite place to haunt. thanks. eric. On Tue, 2003-10-07 at 17:15, Derek Atkins wrote: > Read RFC-82* -- the messageID is a unique identifier. It usually > includes a data+timestamp, ip address or hostname, and other > information to attempt to make the ID 'unique'. > > -derek > > eric <235u at comcast.net> writes: > > > hi, i sent an email to myself and was slightly surprised to see the name > > of my computer listed. (playPen1). > > > > Message-Id: <1065558318.18652.1.camel at playPen1> > > > > 1. what do the numbers and "camel" mean? > > 2. where is there a good explanation of what information is passed > > along with an email? thanks for any hints. eric. > > -- > > Check out http://home.comcast.net/~235u > > "Loki_the_Doppelganger" > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.blu.org/pipermail/discuss/attachments/20031007/283a72cc/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |