[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [SLUG] Using X-message in headers.

To: "Rodos" <rodos@nospam.haywood.org>, <slug@nospam.slug.org.au>
Subject: RE: [SLUG] Using X-message in headers.
From: "David Kempe" <david@nospam.solutionsfirst.net>
Date: Thu, 15 Jun 2000 17:45:06 +1000
Importance: Normal
In-Reply-To: <Pine.LNX.4.10.10006151429090.4135-100000@nospam.reed.rodos.net>
Sender: owner-slug@nospam.newtreno.spectrum.com.au

Anyone know what the x-message header is really for? I searched the RFC's
> and could not find anything.

http://www.oac.uci.edu/indiv/ehood/MIME/2047/rfc2047.html

That seems to suggest something like this:

An 'encoded-word' may replace a 'text' token (as defined by RFC 822) in any
Subject or Comments header field, any extension message header field, or any
MIME body part field for which the field body is defined as '*text'. An
'encoded-word' may also appear in any user-defined ("X-") message or body
part header field.

Under section 5

Dave

______________________________
solutionsFirst.net Consulting
http://solutionsfirst.net
Ph: (02) 9555 4847
Fax: (02) 9818 7711
Mob: 0413 022 143

--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to slug-request@nospam.slug.org.au with
unsubscribe in the text

References:
- [SLUG] Using X-message in headers.
  - From: Rodos <rodos@nospam.haywood.org>

Prev by Date: Re: [SLUG] Using X-message in headers.
Next by Date: [SLUG] cron / crontab
Prev by thread: Re: [SLUG] Using X-message in headers.
Next by thread: [SLUG] cron / crontab
Index(es):
- Date
- Thread