From owner-ietf-fax@mail.imc.org Sun Apr 1 20:29:41 2001 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA03097 for ; Sun, 1 Apr 2001 20:29:40 -0400 (EDT) Received: by above.proper.com (8.9.3/8.9.3) id QAA05424 for ietf-fax-bks; Sun, 1 Apr 2001 16:48:34 -0700 (PDT) Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10]) by above.proper.com (8.9.3/8.9.3) with ESMTP id QAA05420 for ; Sun, 1 Apr 2001 16:48:28 -0700 (PDT) Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74]) by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA14829; Mon, 2 Apr 2001 08:48:25 +0900 (JST) Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10]) by azteca.isd.ricoh.co.jp (Mirapoint) with SMTP id AAG40270; Mon, 2 Apr 2001 08:48:24 +0900 (JST) Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA22824; Mon, 2 Apr 2001 08:48:22 +0900 To: ietf-fax@imc.org Cc: Claudio.Allocchio@elettra.trieste.it Subject: Re: Draft minutes at Minneapolis In-Reply-To: <20010325151638P.tamura@toda.ricoh.co.jp> References: <20010325151638P.tamura@toda.ricoh.co.jp> X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010402085619U.tamura@toda.ricoh.co.jp> Date: Mon, 02 Apr 2001 08:56:19 +0900 (JST) From: Hiroshi Tamura X-Dispatcher: imput version 20000228(IM140) Lines: 28 Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Folks, There are no comments about FAX-WG meeting minutes at Minneapolis. I will submit it as it is, sooner or later. From: Hiroshi Tamura Subject: Draft minutes at Minneapolis Date: Sun, 25 Mar 2001 15:16:38 +0900 (JST) > Folks, > > I'm back. > > Attached is our draft minutes at Minneapolis. If there are comments, > correction or something, please let us know by the end of March. > ^^^^^^^^^^^^^^^^^^^ > > We will submit it at beginning of April to IETF. > > Again, thanks to Graham for the base for the report. > Also, thanks to Claudio for your *detailed* summary. > > Regards, -- Hiroshi Tamura, Co-chair of IETF-FAX WG E-mail: tamura@toda.ricoh.co.jp From owner-ietf-fax@mail.imc.org Mon Apr 2 19:48:52 2001 Received: from above.proper.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04316 for ; Mon, 2 Apr 2001 19:48:51 -0400 (EDT) Received: by above.proper.com (8.9.3/8.9.3) id QAA26759 for ietf-fax-bks; Mon, 2 Apr 2001 16:18:15 -0700 (PDT) Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10]) by above.proper.com (8.9.3/8.9.3) with ESMTP id QAA26755 for ; Mon, 2 Apr 2001 16:18:13 -0700 (PDT) Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74]) by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA12550 for ; Tue, 3 Apr 2001 08:18:15 +0900 (JST) Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10]) by azteca.isd.ricoh.co.jp (Mirapoint) with SMTP id AAG54364; Tue, 3 Apr 2001 08:18:14 +0900 (JST) Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA02280 for ; Tue, 3 Apr 2001 08:18:12 +0900 To: ietf-fax@imc.org Subject: WG Last Call for draft-ietf-fax-service-v2-03.txt X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010403082611F.tamura@toda.ricoh.co.jp> Date: Tue, 03 Apr 2001 08:26:11 +0900 (JST) From: Hiroshi Tamura X-Dispatcher: imput version 20000228(IM140) Lines: 36 Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Folks, This is a Working Group Last Call notice. As we confirmed and Ned agreed at Minneapolis meeting, we can do WG Last Call for draft-ietf-fax-service-v2-03.txt as Draft Standard, although there are dependency issues. (Please see our minutes for the details.) Here is the summary. ---------------------------------------------------------------------- A Simple Mode of Facsimile Using Internet Mail - draft-ietf-fax-service-v2-03.txt - SUMMARY This specification provides for "simple mode" carriage of facsimile data over the Internet. The specification employs standard protocols and file formats such as TCP/IP, Internet mail protocols, MIME, and TIFF for Facsimile. It can send images not only to other Internet-aware facsimile devices but also to Internet-native systems, such as PCs with common email readers which can handle MIME mail and TIFF for Facsimile data. The specification facilitates communication among existing facsimile devices, Internet mail agents, and the gateways which connect them. ---------------------------------------------------------------------- The WG Last Call period is 2 weeks. It closes on April 17. If you have "last comments", please send them to our ML by April 17. Regards, -- Hiroshi Tamura IETF FAX WG co-chair From owner-ietf-fax@mail.imc.org Thu Apr 5 07:08:49 2001 Received: from above.proper.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA27522 for ; Thu, 5 Apr 2001 07:08:48 -0400 (EDT) Received: by above.proper.com (8.9.3/8.9.3) id DAA02730 for ietf-fax-bks; Thu, 5 Apr 2001 03:39:24 -0700 (PDT) Received: from plmta00.chello.pl (plmta00.chello.pl [213.46.248.62]) by above.proper.com (8.9.3/8.9.3) with ESMTP id DAA02723 for ; Thu, 5 Apr 2001 03:39:22 -0700 (PDT) Message-Id: <200104051039.DAA02723@above.proper.com> Received: from hetnet.nl ([213.93.48.181]) by plmta00.chello.pl (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with SMTP id pl for ; Thu, 5 Apr 2001 08:01:07 -0100 From: "Rita de Groot" To: Subject: huidziekte Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 5 Apr 2001 10:58:38 +0200 Content-Transfer-Encoding: 8bit Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8bit Vijf jaar voordat deze foto's werden genomen werd bij mij diagnose reumatische artritis gesteld en als zodanig ook behandeld. Niets hielp. Toen de ziekte zich zo manifesteerde zoals u hieronder kunt zien.......... http://www.naardedokter.com/testimonials/sys_lup_eryth.htm From owner-ietf-fax@mail.imc.org Thu Apr 5 07:36:04 2001 Received: from above.proper.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA28033 for ; Thu, 5 Apr 2001 07:36:03 -0400 (EDT) Received: by above.proper.com (8.9.3/8.9.3) id EAA05366 for ietf-fax-bks; Thu, 5 Apr 2001 04:06:50 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.9.3/8.9.3) with ESMTP id EAA05362 for ; Thu, 5 Apr 2001 04:06:48 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27388; Thu, 5 Apr 2001 07:06:47 -0400 (EDT) Message-Id: <200104051106.HAA27388@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-fax@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-fax-implementers-guide-07.txt Date: Thu, 05 Apr 2001 07:06:47 -0400 Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Fax Working Group of the IETF. Title : Implementers Guide for Facsimile Using Internet Mail Author(s) : V. Cancio, M. Moldovan, H. Tamura, D. Wing Filename : draft-ietf-fax-implementers-guide-07.txt Pages : 24 Date : 04-Apr-01 This document is intended for the implementers of software which uses email to send to facsimiles using RFC 2305 and 2532. This is an informational document and its guidelines do not supersede the referenced documents. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-fax-implementers-guide-07.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-fax-implementers-guide-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-fax-implementers-guide-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20010404074848.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-fax-implementers-guide-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-fax-implementers-guide-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010404074848.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-fax@mail.imc.org Thu Apr 5 21:39:39 2001 Received: from above.proper.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA18612 for ; Thu, 5 Apr 2001 21:39:38 -0400 (EDT) Received: by above.proper.com (8.9.3/8.9.3) id SAA01534 for ietf-fax-bks; Thu, 5 Apr 2001 18:07:16 -0700 (PDT) Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10]) by above.proper.com (8.9.3/8.9.3) with ESMTP id SAA01529 for ; Thu, 5 Apr 2001 18:07:14 -0700 (PDT) Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75]) by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id KAA18316 for ; Fri, 6 Apr 2001 10:06:14 +0900 (JST) Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10]) by delsol.isd.ricoh.co.jp (Mirapoint) with SMTP id AAH47329; Fri, 6 Apr 2001 10:05:28 +0900 (JST) Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id KAA05821 for ; Fri, 6 Apr 2001 10:05:25 +0900 To: ietf-fax@imc.org Subject: Re: I-D ACTION:draft-ietf-fax-implementers-guide-07.txt In-Reply-To: <200104051106.HAA27388@ietf.org> References: <200104051106.HAA27388@ietf.org> X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010406101329L.tamura@toda.ricoh.co.jp> Date: Fri, 06 Apr 2001 10:13:29 +0900 (JST) From: Hiroshi Tamura X-Dispatcher: imput version 20000228(IM140) Lines: 13 Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit Folks, I modified according to the suggesions during the WG Last Call last month. We agreed at Minneapolis that new WG LC is not necessary for this I-D. Sooner or later, we request IESG consideration as Informational RFC. Regards, -- Hiroshi Tamura, Ricoh Company, LTD. E-mail: tamura@toda.ricoh.co.jp From owner-ietf-fax@mail.imc.org Sat Apr 14 12:22:08 2001 Received: from above.proper.com ([208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13519 for ; Sat, 14 Apr 2001 12:22:07 -0400 (EDT) Received: (from majordomo@localhost) by above.proper.com (8.9.3/8.9.3) id IAA15836 for ietf-fax-bks; Sat, 14 Apr 2001 08:46:18 -0700 (PDT) Received: from KVRA ([211.217.77.46]) by above.proper.com (8.9.3/8.9.3) with ESMTP id IAA14071; Sat, 14 Apr 2001 08:39:40 -0700 (PDT) From: Sabrina_B@btts.net Message-ID: <000079eb7bf9$0000089b$000056d3@btts.net> To: Subject: Customer Care Center 22227 Date: Fri, 13 Apr 2001 06:05:59 -0800 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 1 X-MSMail-Priority: High Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: quoted-printable = Take Control Of Your Conference Calls
Why Pay=
 More For Your Confere=
nce Calls?
Onl=
y .18 Cents per minute (Including long distance!)
=

          • =
No setup fees
          • No contracts or monthly fees
          • Call=
 anytime, from anywhere, to anywhere
          • International Dial In 18 cents per minut=
e
          • C=
onnects up to 100 participants
          • Operator Help available 24/7
            <=
/LI>
=
Get the best quality, the easiest to use,=
 and lowest rate in the industry.
<=
TR>
<=
FONT color=3D#ff0000 size=3D2>Required Input Field*
If you like saving money, fill out the form below and one of=
 our consultants will contact you.
<=
TBODY>
Web Address*
<=
/TR> <=
TD width=3D"51%"> <=
TR>
Name*
 
 
Company Name*
State
 
Business Phone*
 <=
/TD>
Home Phone
E-mail*
 
Type of Business
 =


       =
;            &=
nbsp;           &nb=
sp;  


This c=
ould be your ad!
Click here to e-mail us your contact info.
This email is to those persons that have contacted Con=
ference Calls for Less regarding available services or product information=
.  If this email is reaching you in error and you feel that you have not c=
ontacted us, click here. We apologize and will gladly remove you from our mail=
ing list.









From owner-ietf-fax@mail.imc.org  Mon Apr 16 07:28:06 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA02314
	for ; Mon, 16 Apr 2001 07:28:06 -0400 (EDT)
Received: by above.proper.com (8.9.3/8.9.3) id DAA18783
	for ietf-fax-bks; Mon, 16 Apr 2001 03:55:25 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id DAA18772
	for ; Mon, 16 Apr 2001 03:55:23 -0700 (PDT)
Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id TAA07848
	for ; Mon, 16 Apr 2001 19:55:23 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by azteca.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAJ19362;
	Mon, 16 Apr 2001 19:55:22 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id TAA06440 for ; Mon, 16 Apr 2001 19:55:15 +0900
To: ietf-fax@imc.org
Subject: Re: I-D ACTION:draft-ietf-fax-implementers-guide-07.txt
In-Reply-To: <20010406101329L.tamura@toda.ricoh.co.jp>
References: <200104051106.HAA27388@ietf.org>
	<20010406101329L.tamura@toda.ricoh.co.jp>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010416200341E.tamura@toda.ricoh.co.jp>
Date: Mon, 16 Apr 2001 20:03:41 +0900 (JST)
From: Hiroshi Tamura 
X-Dispatcher: imput version 20000228(IM140)
Lines: 15
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 
Content-Transfer-Encoding: 7bit

Folks,

> I modified according to the suggesions during the WG Last Call
> last month. We agreed at Minneapolis that new WG LC is not necessary
> for this I-D.
> 
> Sooner or later, we request IESG consideration as Informational RFC.

In fact, Claudio did last week.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Tue Apr 17 10:39:32 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA08823
	for ; Tue, 17 Apr 2001 10:39:30 -0400 (EDT)
Received: by above.proper.com (8.9.3/8.9.3) id HAA18541
	for ietf-fax-bks; Tue, 17 Apr 2001 07:03:08 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id HAA18533
	for ; Tue, 17 Apr 2001 07:03:05 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07938;
	Tue, 17 Apr 2001 10:03:04 -0400 (EDT)
Message-Id: <200104171403.KAA07938@ietf.org>
To: IETF-Announce: ;
Cc: ietf-fax@imc.org
From: The IESG 
SUBJECT: Last Call: Minimal GSTN address format in Internet Mail to
	 Draft Standard
Reply-to: iesg@ietf.org
Date: Tue, 17 Apr 2001 10:03:04 -0400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 


The IESG has received a request from the Internet Fax Working Group to
consider Minimal GSTN address format in Internet Mail
 as a Draft Standard, replacing
RFC2303, currently a Proposed Standard.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by April 30, 2001.

Implementation Report can be found at
http://www.ietf.org/IESG/Implementations/RFC2303-Implementation.txt

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-fax-minaddr-v2-03.txt




From owner-ietf-fax@mail.imc.org  Tue Apr 17 10:44:23 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA08916
	for ; Tue, 17 Apr 2001 10:44:22 -0400 (EDT)
Received: by above.proper.com (8.9.3/8.9.3) id HAA19425
	for ietf-fax-bks; Tue, 17 Apr 2001 07:15:41 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id HAA19419
	for ; Tue, 17 Apr 2001 07:15:39 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08262;
	Tue, 17 Apr 2001 10:15:38 -0400 (EDT)
Message-Id: <200104171415.KAA08262@ietf.org>
To: IETF-Announce: ;
Cc: ietf-fax@imc.org
From: The IESG 
SUBJECT: Last Call: Minimal FAX address format in Internet Mail to
	 Draft Standard
Reply-to: iesg@ietf.org
Date: Tue, 17 Apr 2001 10:15:38 -0400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 


The IESG has received a request from the Internet Fax Working Group to
consider Minimal FAX address format in Internet Mail
 as a Draft Standard, replacing
RFC2304, a Proposed Standard.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by April 30, 2001.

Implementation Report can be found at
http://www.ietf.org/IESG/Implementations/RFC2304.txt

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-fax-faxaddr-v2-03.txt


From owner-ietf-fax@mail.imc.org  Tue Apr 24 15:25:54 2001
Received: from above.proper.com ([208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13510
	for ; Tue, 24 Apr 2001 15:25:53 -0400 (EDT)
Received: by above.proper.com (8.9.3/8.9.3) id LAA08707
	for ietf-fax-bks; Tue, 24 Apr 2001 11:56:17 -0700 (PDT)
Received: from gaganan.com ([168.126.237.43])
	by above.proper.com (8.9.3/8.9.3) with SMTP id LAA08674
	for ; Tue, 24 Apr 2001 11:56:08 -0700 (PDT)
Message-Id: <200104241856.LAA08674@above.proper.com>
From: "Son Ho Jin" 
To: "julia@vental.com"julia@vental.com
Subject: I got it
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Date: Wed, 25 Apr 2001 03:56:45 +0900
Content-Transfer-Encoding: 8bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 
Content-Transfer-Encoding: 8bit

Hey, lu

Sorry, it took longer than i expected but I found the site, it's

 http://www.multiopen.com
 
 the site will make your web surfing very convenient.
 
 
And here goes one more, it's

 http://www.mysimon.com 
 
 this one will help your online shopping    
 
 Get to the site and mail me after

 bye~
 




From owner-ietf-fax@mail.imc.org  Wed Apr 25 01:31:27 2001
Received: from above.proper.com ([208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA27991
	for ; Wed, 25 Apr 2001 01:31:26 -0400 (EDT)
Received: (from majordomo@localhost)
	by above.proper.com (8.9.3/8.9.3) id VAA14283
	for ietf-fax-bks; Tue, 24 Apr 2001 21:55:19 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id VAA14278
	for ; Tue, 24 Apr 2001 21:55:17 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id NAA04650
	for ; Wed, 25 Apr 2001 13:55:17 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAK27189;
	Wed, 25 Apr 2001 13:55:16 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id NAA23103 for ; Wed, 25 Apr 2001 13:55:12 +0900
To: ietf-fax@imc.org
Subject: RFC2821 and RFC2822
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Wed_Apr_25_13:55:15_2001_955)--"
Content-Transfer-Encoding: 7bit
Message-Id: <20010425135545P.tamura@toda.ricoh.co.jp>
Date: Wed, 25 Apr 2001 13:55:45 +0900 (JST)
From: Hiroshi Tamura 
X-Dispatcher: imput version 20000228(IM140)
Lines: 340
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 

----Next_Part(Wed_Apr_25_13:55:15_2001_955)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Folks,

For your information, I forward the attached announce to our ML,
although lots of people may already know it.

--
Hiroshi Tamura, Co-Chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



----Next_Part(Wed_Apr_25_13:55:15_2001_955)--
Content-Type: message/rfc822

Received: from dsp2.toda.ricoh.co.jp (dsp2.toda.ricoh.co.jp [133.139.21.15]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA20648 for ; Wed, 25 Apr 2001 08:46:45 +0900
Received: from siosai.isd.ricoh.co.jp (siosai.isd.ricoh.co.jp [133.139.250.77]) by dsp2.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0M8sun) with ESMTP id IAA25978 for ; Wed, 25 Apr 2001 08:46:47 +0900
Received: from mail.notes.ricoh.co.jp (helios.isd.ricoh.co.jp [133.139.250.61] (may be forged))
	by siosai.isd.ricoh.co.jp (Mirapoint)
	with ESMTP id AAP55206;
	Wed, 25 Apr 2001 08:46:46 +0900 (JST)
Received: from cs.utk.edu (cs.utk.edu [160.36.56.56])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA05490
	for ; Wed, 25 Apr 2001 08:46:44 +0900 (JST)
Received: from localhost (daemon@localhost) 
        by cs.utk.edu with SMTP (cf v2.9s-UTK)
	id TAA28805; Tue, 24 Apr 2001 19:46:15 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Tue, 24 Apr 2001 19:45:33 -0400
Received:  
        by cs.utk.edu (cf v2.9s-UTK)
	id TAA28663; Tue, 24 Apr 2001 19:45:33 -0400 (EDT)
Received: from boreas.isi.edu (marvin@localhost) 
        by cs.utk.edu with ESMTP (cf v2.9s-UTK)
	id TAA28649; Tue, 24 Apr 2001 19:45:31 -0400 (EDT)
Received: from boreas.isi.edu (128.9.160.161 -> boreas.isi.edu)
 by cs.utk.edu (smtpshim v1.0); Tue, 24 Apr 2001 19:45:31 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f3ONjN528877;
	Tue, 24 Apr 2001 16:45:23 -0700 (PDT)
Message-Id: <200104242345.f3ONjN528877@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2821 on Simple Mail Transfer Protocol
Cc: rfc-ed@ISI.EDU, drums@cs.utk.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 24 Apr 2001 16:45:23 -0700
X-UIDL: 988156130.000
From: RFC Editor 
List-Unsubscribe: 
Status: U


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2821

        Title:	    Simple Mail Transfer Protocol
        Author(s):  J. Klensin, Editor
        Status:     Standards Track
	Date:       April 2001
        Mailbox:    klensin@research.att.com
        Pages:      79
        Characters: 192504
        Updates:    1123
        Obsoletes:  821, 974

        I-D Tag:    draft-ietf-drums-smtpupd-13.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc2821.txt


This document is a self-contained specification of the basic protocol
for the Internet electronic mail transport.  It consolidates, updates
and clarifies, but doesn't add new or change existing functionality of
the following:
 
-  the original SMTP (Simple Mail Transfer Protocol) specification of
   RFC 821,
 
-  domain name system requirements and implications for mail
   transport from RFC 1035 and RFC 974,
 
-  the clarifications and applicability statements in RFC 1123,
   and
 
-  material drawn from the SMTP Extension mechanisms.
 
It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the
mail transport materials of RFC 1123).  However, RFC 821 specifies
some features that were not in significant use in the Internet by the
mid-1990s and (in appendices) some additional transport models.  Those
sections are omitted here in the interest of clarity and brevity;
readers needing them should refer to RFC 821.

It also includes some additional material from RFC 1123 that required
amplification.  This material has been identified in multiple ways,
mostly by tracking flaming on various lists and newsgroups and
problems of unusual readings or interpretations that have
appeared as the SMTP extensions have been deployed.  Where this
specification moves beyond consolidation and actually differs from
earlier documents, it supersedes them technically as well as
textually.
 
Although SMTP was designed as a mail transport and delivery protocol,
this specification also contains information that is important to its
use as a 'mail submission' protocol, as recommended for POP and IMAP. 

Additional submission issues are discussed in RFC 2476.
 
Section 2.3 provides definitions of terms specific to this document.
Except when the historical terminology is necessary for clarity, this
document uses the current 'client' and 'server' terminology to
identify the sending and receiving SMTP processes, respectively.
 
A companion document discusses message headers, message bodies
and formats and structures for them, and their relationship.

This document is a product of the Detailed Revision/Update of Message
Standards Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <010424164015.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2821

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2821.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <010424164015.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

----Next_Part(Wed_Apr_25_13:55:15_2001_955)--
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit

Received: from dsp2.toda.ricoh.co.jp (dsp2.toda.ricoh.co.jp [133.139.21.15]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA20664 for ; Wed, 25 Apr 2001 08:48:39 +0900
Received: from oasis.isd.ricoh.co.jp (oasis.isd.ricoh.co.jp [133.139.250.76]) by dsp2.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0M8sun) with ESMTP id IAA25994 for ; Wed, 25 Apr 2001 08:48:40 +0900
Received: from mail.notes.ricoh.co.jp (helios.isd.ricoh.co.jp [133.139.250.61] (may be forged))
	by oasis.isd.ricoh.co.jp (Mirapoint)
	with ESMTP id AAT47227;
	Wed, 25 Apr 2001 08:48:39 +0900 (JST)
Received: from cs.utk.edu (cs.utk.edu [160.36.56.56])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA05840
	for ; Wed, 25 Apr 2001 08:48:37 +0900 (JST)
Received: from localhost (daemon@localhost) 
        by cs.utk.edu with SMTP (cf v2.9s-UTK)
	id TAA29239; Tue, 24 Apr 2001 19:48:25 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Tue, 24 Apr 2001 19:48:22 -0400
Received:  
        by cs.utk.edu (cf v2.9s-UTK)
	id TAA29184; Tue, 24 Apr 2001 19:48:21 -0400 (EDT)
Received: from boreas.isi.edu (marvin@localhost) 
        by cs.utk.edu with ESMTP (cf v2.9s-UTK)
	id TAA29169; Tue, 24 Apr 2001 19:48:19 -0400 (EDT)
Received: from boreas.isi.edu (128.9.160.161 -> boreas.isi.edu)
 by cs.utk.edu (smtpshim v1.0); Tue, 24 Apr 2001 19:48:19 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f3ONm9529289;
	Tue, 24 Apr 2001 16:48:09 -0700 (PDT)
Message-Id: <200104242348.f3ONm9529289@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2822 on Internet Message Format
Cc: rfc-ed@ISI.EDU, drums@cs.utk.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 24 Apr 2001 16:48:09 -0700
X-UIDL: 988156130.001
From: RFC Editor 
List-Unsubscribe: 
Status: U


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2822

        Title:	    Internet Message Format
        Author(s):  P. Resnick, Editor
        Status:     Standards Track
	Date:       March 2001
        Mailbox:    presnick@qualcomm.com
        Pages:      50
        Characters: 110695
        Obsoletes:  822

        I-D Tag:    draft-ietf-drums-msg-fmt-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc2822.txt


This standard specifies a syntax for text messages that are sent
between computer users, within the framework of "electronic mail"
messages.  This standard supersedes the one specified in Request For
Comments (RFC) 822, "Standard for the Format of ARPA Internet Text
Messages", updating it to reflect current practice and incorporating
incremental changes that were specified in other RFCs.

This document is a product of the Detailed Revision/Update of Message
Standards Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <010424164548.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2822

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2822.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <010424164548.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

----Next_Part(Wed_Apr_25_13:55:15_2001_955)----


From owner-ietf-fax@mail.imc.org  Wed Apr 25 02:07:02 2001
Received: from above.proper.com ([208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA08247
	for ; Wed, 25 Apr 2001 02:07:01 -0400 (EDT)
Received: (from majordomo@localhost)
	by above.proper.com (8.9.3/8.9.3) id VAA14283
	for ietf-fax-bks; Tue, 24 Apr 2001 21:55:19 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id VAA14278
	for ; Tue, 24 Apr 2001 21:55:17 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id NAA04650
	for ; Wed, 25 Apr 2001 13:55:17 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAK27189;
	Wed, 25 Apr 2001 13:55:16 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id NAA23103 for ; Wed, 25 Apr 2001 13:55:12 +0900
To: ietf-fax@imc.org
Subject: RFC2821 and RFC2822
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Wed_Apr_25_13:55:15_2001_955)--"
Content-Transfer-Encoding: 7bit
Message-Id: <20010425135545P.tamura@toda.ricoh.co.jp>
Date: Wed, 25 Apr 2001 13:55:45 +0900 (JST)
From: Hiroshi Tamura 
X-Dispatcher: imput version 20000228(IM140)
Lines: 340
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 

----Next_Part(Wed_Apr_25_13:55:15_2001_955)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Folks,

For your information, I forward the attached announce to our ML,
although lots of people may already know it.

--
Hiroshi Tamura, Co-Chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



----Next_Part(Wed_Apr_25_13:55:15_2001_955)--
Content-Type: message/rfc822

Received: from dsp2.toda.ricoh.co.jp (dsp2.toda.ricoh.co.jp [133.139.21.15]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA20648 for ; Wed, 25 Apr 2001 08:46:45 +0900
Received: from siosai.isd.ricoh.co.jp (siosai.isd.ricoh.co.jp [133.139.250.77]) by dsp2.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0M8sun) with ESMTP id IAA25978 for ; Wed, 25 Apr 2001 08:46:47 +0900
Received: from mail.notes.ricoh.co.jp (helios.isd.ricoh.co.jp [133.139.250.61] (may be forged))
	by siosai.isd.ricoh.co.jp (Mirapoint)
	with ESMTP id AAP55206;
	Wed, 25 Apr 2001 08:46:46 +0900 (JST)
Received: from cs.utk.edu (cs.utk.edu [160.36.56.56])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA05490
	for ; Wed, 25 Apr 2001 08:46:44 +0900 (JST)
Received: from localhost (daemon@localhost) 
        by cs.utk.edu with SMTP (cf v2.9s-UTK)
	id TAA28805; Tue, 24 Apr 2001 19:46:15 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Tue, 24 Apr 2001 19:45:33 -0400
Received:  
        by cs.utk.edu (cf v2.9s-UTK)
	id TAA28663; Tue, 24 Apr 2001 19:45:33 -0400 (EDT)
Received: from boreas.isi.edu (marvin@localhost) 
        by cs.utk.edu with ESMTP (cf v2.9s-UTK)
	id TAA28649; Tue, 24 Apr 2001 19:45:31 -0400 (EDT)
Received: from boreas.isi.edu (128.9.160.161 -> boreas.isi.edu)
 by cs.utk.edu (smtpshim v1.0); Tue, 24 Apr 2001 19:45:31 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f3ONjN528877;
	Tue, 24 Apr 2001 16:45:23 -0700 (PDT)
Message-Id: <200104242345.f3ONjN528877@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2821 on Simple Mail Transfer Protocol
Cc: rfc-ed@ISI.EDU, drums@cs.utk.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 24 Apr 2001 16:45:23 -0700
X-UIDL: 988156130.000
From: RFC Editor 
List-Unsubscribe: 
Status: U


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2821

        Title:	    Simple Mail Transfer Protocol
        Author(s):  J. Klensin, Editor
        Status:     Standards Track
	Date:       April 2001
        Mailbox:    klensin@research.att.com
        Pages:      79
        Characters: 192504
        Updates:    1123
        Obsoletes:  821, 974

        I-D Tag:    draft-ietf-drums-smtpupd-13.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc2821.txt


This document is a self-contained specification of the basic protocol
for the Internet electronic mail transport.  It consolidates, updates
and clarifies, but doesn't add new or change existing functionality of
the following:
 
-  the original SMTP (Simple Mail Transfer Protocol) specification of
   RFC 821,
 
-  domain name system requirements and implications for mail
   transport from RFC 1035 and RFC 974,
 
-  the clarifications and applicability statements in RFC 1123,
   and
 
-  material drawn from the SMTP Extension mechanisms.
 
It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the
mail transport materials of RFC 1123).  However, RFC 821 specifies
some features that were not in significant use in the Internet by the
mid-1990s and (in appendices) some additional transport models.  Those
sections are omitted here in the interest of clarity and brevity;
readers needing them should refer to RFC 821.

It also includes some additional material from RFC 1123 that required
amplification.  This material has been identified in multiple ways,
mostly by tracking flaming on various lists and newsgroups and
problems of unusual readings or interpretations that have
appeared as the SMTP extensions have been deployed.  Where this
specification moves beyond consolidation and actually differs from
earlier documents, it supersedes them technically as well as
textually.
 
Although SMTP was designed as a mail transport and delivery protocol,
this specification also contains information that is important to its
use as a 'mail submission' protocol, as recommended for POP and IMAP. 

Additional submission issues are discussed in RFC 2476.
 
Section 2.3 provides definitions of terms specific to this document.
Except when the historical terminology is necessary for clarity, this
document uses the current 'client' and 'server' terminology to
identify the sending and receiving SMTP processes, respectively.
 
A companion document discusses message headers, message bodies
and formats and structures for them, and their relationship.

This document is a product of the Detailed Revision/Update of Message
Standards Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <010424164015.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2821

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2821.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <010424164015.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

----Next_Part(Wed_Apr_25_13:55:15_2001_955)--
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit

Received: from dsp2.toda.ricoh.co.jp (dsp2.toda.ricoh.co.jp [133.139.21.15]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA20664 for ; Wed, 25 Apr 2001 08:48:39 +0900
Received: from oasis.isd.ricoh.co.jp (oasis.isd.ricoh.co.jp [133.139.250.76]) by dsp2.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0M8sun) with ESMTP id IAA25994 for ; Wed, 25 Apr 2001 08:48:40 +0900
Received: from mail.notes.ricoh.co.jp (helios.isd.ricoh.co.jp [133.139.250.61] (may be forged))
	by oasis.isd.ricoh.co.jp (Mirapoint)
	with ESMTP id AAT47227;
	Wed, 25 Apr 2001 08:48:39 +0900 (JST)
Received: from cs.utk.edu (cs.utk.edu [160.36.56.56])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA05840
	for ; Wed, 25 Apr 2001 08:48:37 +0900 (JST)
Received: from localhost (daemon@localhost) 
        by cs.utk.edu with SMTP (cf v2.9s-UTK)
	id TAA29239; Tue, 24 Apr 2001 19:48:25 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Tue, 24 Apr 2001 19:48:22 -0400
Received:  
        by cs.utk.edu (cf v2.9s-UTK)
	id TAA29184; Tue, 24 Apr 2001 19:48:21 -0400 (EDT)
Received: from boreas.isi.edu (marvin@localhost) 
        by cs.utk.edu with ESMTP (cf v2.9s-UTK)
	id TAA29169; Tue, 24 Apr 2001 19:48:19 -0400 (EDT)
Received: from boreas.isi.edu (128.9.160.161 -> boreas.isi.edu)
 by cs.utk.edu (smtpshim v1.0); Tue, 24 Apr 2001 19:48:19 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f3ONm9529289;
	Tue, 24 Apr 2001 16:48:09 -0700 (PDT)
Message-Id: <200104242348.f3ONm9529289@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2822 on Internet Message Format
Cc: rfc-ed@ISI.EDU, drums@cs.utk.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 24 Apr 2001 16:48:09 -0700
X-UIDL: 988156130.001
From: RFC Editor 
List-Unsubscribe: 
Status: U


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2822

        Title:	    Internet Message Format
        Author(s):  P. Resnick, Editor
        Status:     Standards Track
	Date:       March 2001
        Mailbox:    presnick@qualcomm.com
        Pages:      50
        Characters: 110695
        Obsoletes:  822

        I-D Tag:    draft-ietf-drums-msg-fmt-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc2822.txt


This standard specifies a syntax for text messages that are sent
between computer users, within the framework of "electronic mail"
messages.  This standard supersedes the one specified in Request For
Comments (RFC) 822, "Standard for the Format of ARPA Internet Text
Messages", updating it to reflect current practice and incorporating
incremental changes that were specified in other RFCs.

This document is a product of the Detailed Revision/Update of Message
Standards Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <010424164548.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2822

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2822.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <010424164548.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

----Next_Part(Wed_Apr_25_13:55:15_2001_955)----


From owner-ietf-fax@mail.imc.org  Mon Apr 30 02:57:59 2001
Received: from above.proper.com ([208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02013
	for ; Mon, 30 Apr 2001 02:57:58 -0400 (EDT)
Received: by above.proper.com (8.9.3/8.9.3) id XAA01981
	for ietf-fax-bks; Sun, 29 Apr 2001 23:31:24 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id XAA01973
	for ; Sun, 29 Apr 2001 23:31:22 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id PAA24605;
	Mon, 30 Apr 2001 15:31:16 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAK89937;
	Mon, 30 Apr 2001 15:31:13 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id PAA28528; Mon, 30 Apr 2001 15:31:08 +0900
To: ietf-fax@imc.org
Cc: ktoyoda@rdmg.mgcs.mei.co.jp
Subject: Re: WG Last Call for draft-ietf-fax-service-v2-03.txt
In-Reply-To: <20010403082611F.tamura@toda.ricoh.co.jp>
References: <20010403082611F.tamura@toda.ricoh.co.jp>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010430153150C.tamura@toda.ricoh.co.jp>
Date: Mon, 30 Apr 2001 15:31:50 +0900 (JST)
From: Hiroshi Tamura 
X-Dispatcher: imput version 20000228(IM140)
Lines: 63
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 
Content-Transfer-Encoding: 7bit

Folks,

(Sorry for my slow action.)

This is the result of IETF-FAX WG Last Call of 
draft-ietf-fax-service-v2-03.txt.

These were submitted for IETF FAX WG Last CALL on April 3, 2001.
During the two-weeks Last Call period, there were no comments.

Therefore, as we confirmed at the Minneapolis meeting,
we can submit it to the IESG with the interworking report
for Draft Standard consideration.
(But, it is not publised until all dependencies are resolved.)

With regard to the interworking report, Toyoda-san, one of
the editors, will circulate it in our ML.

Regards,
--
Hiroshi Tamura
IETF FAX WG co-chair

From: Hiroshi Tamura 
Subject: WG Last Call for draft-ietf-fax-service-v2-03.txt
Date: Tue, 03 Apr 2001 08:26:11 +0900 (JST)

> Folks,
> 
> This is a Working Group Last Call notice.
> 
> As we confirmed and Ned agreed at Minneapolis meeting,
> we can do WG Last Call for draft-ietf-fax-service-v2-03.txt
> as Draft Standard, although there are dependency issues.
> (Please see our minutes for the details.)
> 
> Here is the summary.
> 
> ----------------------------------------------------------------------
> A Simple Mode of Facsimile Using Internet Mail
> - draft-ietf-fax-service-v2-03.txt -
> 
> SUMMARY
> 
> This specification provides for "simple mode" carriage of facsimile
> data over the Internet. 
> The specification employs standard protocols and file formats such 
> as TCP/IP, Internet mail protocols, MIME, and TIFF for Facsimile.  
> It can send images not only to other Internet-aware facsimile devices 
> but also to Internet-native systems, such as PCs with common email 
> readers which can handle MIME mail and TIFF for Facsimile data.  
> The specification facilitates communication among existing facsimile 
> devices, Internet mail agents, and the gateways which connect them.
> 
> ----------------------------------------------------------------------
> 
> The WG Last Call period is 2 weeks. It closes on April 17.
> If you have "last comments", please send them to our ML by April 17.
> 
> Regards,
> --
> Hiroshi Tamura
> IETF FAX WG co-chair


From owner-ietf-fax@mail.imc.org  Mon Apr 30 03:36:09 2001
Received: from above.proper.com ([208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02346
	for ; Mon, 30 Apr 2001 03:36:08 -0400 (EDT)
Received: (from majordomo@localhost)
	by above.proper.com (8.9.3/8.9.3) id AAA07856
	for ietf-fax-bks; Mon, 30 Apr 2001 00:09:21 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id AAA07847
	for ; Mon, 30 Apr 2001 00:09:19 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id QAA27466
	for ; Mon, 30 Apr 2001 16:09:18 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAK90040;
	Mon, 30 Apr 2001 16:09:17 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id QAA28696 for ; Mon, 30 Apr 2001 16:09:11 +0900
To: ietf-fax@imc.org
Subject: Draft communication letter to ITU-T
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010430160954A.tamura@toda.ricoh.co.jp>
Date: Mon, 30 Apr 2001 16:09:54 +0900 (JST)
From: Hiroshi Tamura 
X-Dispatcher: imput version 20000228(IM140)
Lines: 147
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 
Content-Transfer-Encoding: 7bit

Folks,

Draft communication letter to ITU-T is below.
Next ITU-T SG16 meeting is held from May 28 to June 8.

If you have comments, please say by May 10.
                                    ^^^^^^^
[[[]]] is only for this mail. 

------------------------------------------------------------------------

Communication from IETF FAX Working Group on Response for Full Mode and
Terminal Mode and the summary of current activities

Abstract
This letter is to respond to the request made by Q.14/SG16 in the November
SG16 meeting. It also includes current FAX WG activities in relation to T.37.


Introduction
Since November, FAX WG had two meetings last December and last March.
The letter from Q.14/SG16 was inputted to the WG meeting.

1 Response for Full Mode and Terminal Mode
1.1 Full Mode
a)FFPIM
The ITU-T is worried that FFPIM may no longer be discussed in IETF,
since draft-ietf-fax-ffpim-00.txt has been deleted from the IETF data base.
ITU-T requests a new version of FFPIM draft to keep discussion going on
in IETF and a further communication to the ITU-T about it's status.

[[[The 4 lines are originally from ITU-T.]]]

->
The WG has already the new version: draft-ietf-fax-ffpim-01.txt.
Please check it at the IETF site.

b)Full Mode
Item b) in the section 2 Response on Full Mode is not sufficient for
the ITU-T request, that describes there is no direct discussion in IETF
Fax WG about Item b) Fax processed status information. Fax processed status
such as number of pages received and error page number are very important
for Internet Fax Full Mode to perform same level of confirmation as G3fax.
Since the Fax WG is not the WG to handle about the issue as the IETF Fax WG
co-chair explained, ITU-T people will write IETF Internet Draft for the issue
under the consultation of the IETF FAX WG chair.
Item a) and c) in the section 2 were accepted

[[[The above 9 lines are originally from ITU-T.]]]

->
Fortunately, The WG started discussing this issue. There is one I-D:
draft-maeda-faxwg-fax-processing-status-00.txt. (It is updated to -01
in our ML, but, you can only find as -00 at the IETF site.) It addresses
the fax processing status such as the information about successful
received pages, using MDN extension field.
We believe that the I-D meets your requests.

The WG agrees to add it in the milestone. The targeted WG Last Call is
December IETF meeting.

1.2 Terminal Mode
T.37 Terminal Mode which supports the transfer of image data, capabilities
exchange and confirmation for Store and Forward internet fax terminals
having limited memory and small CPU power, was proposed in the meeting.
The Terminal Mode extends Internet fax capabilities to enable all features
of Group 3 facsimile to be supported on the Internet using T.30 signals
in capability exchange. The mode will be implemented on G3FAX based
Internet Fax terminals which communicate using G3 mode in PSTN and
Terminal Mode in Internet. The terminal may have gateway functions
between G3Fax and Internet Fax Terminal Mode. The one of the objectives
of Terminal Mode is a simple protocol for ROM oriented fax devices not
for PC based E-mail client. The Terminal Mode may not be able to communicate
to Simple Mode and Full Mode directory. 
(1)Is it able to add Terminal Mode in the charter of Fax WG
for technical discussion in IETF?
(2)If the charter will not be able amended to discuss Terminal Mode
in the Fax WG, IETF is requested to provide reasons for their decisions
with required to whether proceed or not proceed the Terminal Mode in IETF.

[[[The above 17 lines are originally from ITU-T.]]]

->
Fortunately, our WG also started discussing it. There are two I-Ds:
draft-maeda-faxwg-terminal-mode-goals-00.txt and
draft-maeda-faxwg-terminal-mode-protocol-00.txt. (They are updated to -01
in our ML, but, you can only find as -00 at the IETF site.). They include
almost the same proposal as the one in ITU-T. With regard to adding it
in the WG's charter, some items under discussion could reach to agreement
without modifying the WG's charter. The WG are not sure that all of them
can be included in it. It depends on the future discussion.

The WG agrees to add it in the milestone. The targeted WG Last Call is
December IETF meeting.

2 Current FAX WG's activities in relation to T.37
2.1 Draft Standard Consideration on Simple mode RFCs
There are the following I-Ds that the WG is now requesting to IESG
for Draft Standard consideration.
- draft-ietf-fax-tiff-fx-09.txt (that will obsolete RFC 2301)
- draft-ietf-fax-minaddr-v2-03.txt (that will obsolete RFC 2303)
- draft-ietf-fax-faxaddr-v2-03.txt (that will obsolete RFC 2304)
Along with draft-ietf-fax-tiff-fx-09.txt, the group is requesting
draft-ietf-fax-tiff-regbis-02.txt that will obsolete RFC 2302 should be BCP.
IESG already checked the contents, therefore, the WG thinks IESG will
approve them soon.

With regard to RFC 2305, there is a draft-ietf-fax-service-v2-03.txt.
The WG Last Call has already finished. Sooner or later, the WG will request
to IESG for Draft Standard consideration. But, it has a dependency issues.
In order to become Draft Standard, all normative references must be
Draft Standard. It refers RFC 2301, 2304 and 1894 normatively.
These are not Draft Standard, but some WGs including FAX WG are trying
to move them to Draft Standard. After all of them becomes Draft Standard,
this I-D will be publised.

2.2 Implementer's guide
The I-D draft-ietf-fax-implementers-guide-07.txt addresses implementation
guidance for published RFCs such as RFC 2301, RFC 2305 and RFC 2532.
It is at the final stage. The WG Last Call has already finished.
The WG has requested IESG consideration for informational RFC.

The WG understands that T.37 will refer it in some ways. After it becomes
RFC, The WG will notify it.

2.3 Otheres
The WG is also discussing both FFPIM(Full-mode Fax Profile for Internet Mail)
and TIFF-FX extension, which the WG already introduced in the communication
letter that was sent in the last SG16 meeting. For your information,
the latest versions are described below.
- draft-ietf-fax-ffpim-00.txt
- draft-ietf-fax-timely-delivery-01.txt
- draft-ietf-fax-content-negotiation-03.txt
- draft-ietf-fax-tiff-fx-extension1-01.txt


Finally...
IETF FAX WG welcomes any comments from Q.14/SG16. The WG hopes the good
relationship can continue.

------------------------------------------------------------------------

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Mon Apr 30 18:37:12 2001
Received: from above.proper.com ([208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27501
	for ; Mon, 30 Apr 2001 18:37:11 -0400 (EDT)
Received: (from majordomo@localhost)
	by above.proper.com (8.9.3/8.9.3) id OAA20547
	for ietf-fax-bks; Mon, 30 Apr 2001 14:57:17 -0700 (PDT)
Received: from outgoing2.themail.com (outgoing.themail.com [216.38.174.37])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id OAA20543
	for ; Mon, 30 Apr 2001 14:57:11 -0700 (PDT)
Date: Mon, 30 Apr 2001 14:57:11 -0700 (PDT)
From: karensutherland@themail.com
Message-Id: <200104302157.OAA20543@above.proper.com>
Received: from mail.TheMail.com [216.38.174.248] by outgoing2.themail.com
  (SMTPD32-6.06) id AF4ED20600D6; Mon, 30 Apr 2001 17:55:26 -0400
Received-From: mail.TheMail.com
To: jameslo@hotmail.com
Cc: iepg@iepg.org, ietf-fax@imc.org, ietf@ietf.org, ifdlh@imap2.asu.edu,
        ifpa@flash.net, iftikhar@erols.com,
        if_i_told_you_then_you_would_know@b.com, ight016@hotmail.com,
        igo211@aol.com, igorprodan@aol.com, iharpi@aol.com,
        ihavefaith@netpass.com, ihrf@ticz.com, iig05-1@htw.uni-sb.de,
        ikajnrn@mobiletel.com, ikao@eecs.wsu.edu, ikao@gandalf.eecs.wsu.edu,
        ike.skelton@mail.house.gov, ikillyou15@hotmail.com, iknowblues@aol.com,
        ikryzano@sd71.bc.ca, ildaron@yahoo.com, ildbjorn@webtv.net,
        ilexx@yahoo.com, ilimajinli@aol.com, ilio_fr@yahoo
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: 
List-ID: 
List-Unsubscribe: 

.fr,illusion@mnsi.net,illustrates@supplement.nihilisme.edu,illustrious@sympatico.ca,illyce333@aol.com,ilmoebiggins@yahoo.net,ilongo@bigfoot.com,ilovechocolate@angelfire.com,iloveschnopps@yahoo.com,ilovethemall311@aol.com,ilpulask-d-request@rootsweb.com,ilpulask-l-request@rootsweb.com,ilpulask-l@rootsweb.com,ilse_jansen@hotmail.com,iluvbirds13@hotmail.com,iluvbirds@hotmail.com,iluvcybersex_69@hotmail.com,iluvj@loveable.com,iluvkline@yahoo.com,ilvsmnspcl@aol.com,
From: karensutherland@themail.com
Subject: ?
X-Priority: 3
Authorized-User: karensutherland@TheMail.com
IP-Address: 204.157.41.54
Reply-To: karensutherland@themail.com
MIME-Version: 1.0
Content-type: text/plain
Message-Id: <200104301755285.SM00142@mail.TheMail.com>
Date: Mon, 30 Apr 2001 17:57:14 -0400

Sexually Attract Women Instantly with nature's secret weapon... Pheromones!!                

Invisible and undetectable, when unknowingly inhaled by any woman, Androstenone
Pheromone Concentrate for men unblocks all restraints and releases her raw
animal sex drive!

This amazing product is sold in stores for $99.95 a bottle. Our price is less...
MUCH LESS! This is the strongest concentration of HUMAN pheromones, allowed by
law, in an essential oil base. It smells great!

Other men will envy your power and success! Wear it just as you would any
cologne and women will be instantly attracted to you. Human pheromones have been
proven to induce sexual desire in women - ALL WOMEN - even the stubborn one's
who were unreceptive to you before! This astonishing fragrance attracts women
like magic!

However, It's not magic - it's science!

Pheromones: Nature's secret attractant

Have you ever noticed how some men are able to attract any woman they want with
hardly any effort? This phenomenon used to be known as 'Animal Magnetism'. Many
scientists now believe that this attraction is due to Pheromones - subtle body
odors that are not consciously detected, but trigger a subconscious sexual
response in the opposite sex.

For years animal pheromones have been used to induce breeding in livestock, but
only recently has Human Pheromone Extract become available and legal in the U.S.

For the first time, in the late 80s, researchers were able to successfully
isolate the human pheromone, Androstenone, found in human sweat. Scientists in
Israel have recently found a way to synthetically reproduce this naturally
occurring aphrodisiac in the laboratory.

This is the one and the ONLY chemical that really attracts women!

No other chemical or compound - natural or synthetic - produces even a tenth of
the excitement in women as Androstenone Pheromone Concentrate

The announcement of this scientific breakthrough, set off a media fire-storm. In
the last few years, the remarkable aphrodisiac qualities of Androstenone
Pheromones have been featured in every major publication, newspaper, national
magazine, and television magazine. From 20/20, Hard Copy, and Dateline NBC, to
the N.Y. times, and the American Journal of Modern Medicine.

Many independent research institutes have conducted studies on the benefits of
Androstenone (You may have heard about the most recent study on CNN.)
Researchers at the University of Kentucky found that women exposed to pictures
of men that had been sprayed with Androstenone found the men far more sexually
attractive than the photos of men that had not been treated.


Androstenone: Human Pheromone
In one study, Androstenone was put through an eight week double blind placebo
controlled scientific study. The results were incredible! Single men who were
using Androstenone, reported suddenly being approached by women in public, women
making eye contact, initiating conversations, etc. Not surprisingly, they were
found to have sex far more often than the men who were not using Androstenone.

In another reported experiment, twin brothers were used in testing. Only one of
the twins was sprayed with the actual pheromones. Women found the brother
wearing the actual Androstenone concentrate, far more sexually attractive than
the other. Now, remember these were identical twins. But time and again, the
women found the twin wearing the human pheromone more attractive hands down.

Androstenone Pheromone Concentrate

There are a number of companies that are selling a blend of pheromones,
typically masked in a musk-like cologne. While a few actually contain synthetic
human pheromones, most do not. Typically, pheromone colognes / body oils contain
a mixture of animal or insect pheromones. This is great if you want to attract
grasshoppers or pigs, but does little to help a man in search of female
companionship.

The Real Thing!

Rather than adding pheromones to an existing cologne, it is our belief, that it
is far more effective to blend a significant amount of pure Androstenone with a
non obtrusive oil base. This creates the strongest concentration of human
pheromones legally available anywhere! THIS IS THE ONLY PHEROMONE OIL PROVEN TO
REALLY WORK! Accept no substitutes!

Incredibly Powerful!

Just a small application of Androstenone Pheromone Concentrate, and you will
suddenly notice women making eye contact, approaching you at the supermarket,
etc. GUARANTEED! Without changing anything else about your presentation, women
will suddenly be far more receptive to your advances.

Sold in stores for $99.95 a bottle (and WELL worth that!) we can offer it to you
directly for only $29.95!!

"Androstenone" comes with a ONE MONTH MONEY-BACK GUARANTEE!  So your one-time
fee is refundable making your decision risk free!  WE GUARANTEE THAT IF YOU ARE
NOT COMPLETELY SATISFIED, JUST RETURN THE UN-USED PORTION WITHIN 30 DAYS AND WE
WILL GIVE YOU A FULL REFUND OF THE PURCHASE PRICE.

***Our normal price for Androstenone is $29.95.  For a limited time only, you
can purchase a 3 MONTH SUPPLY for only $48.95! That is a savings of $40.90 off
our regular price.  We will also continue to offer you the Androstenone at this
low price as long as you purchase from us in the future.  To take advantage of
this savings you must order within the next 10 days.


***********************************************************************
ORDER TODAY:
SEND Only $29.95 US
For Shipping OUTSIDE the US please add $11.00.
or
3 MONTH SUPPLY for only $48.95!
(CHECK, OR MONEY ORDER)
Shipping is included for US Shipments! For Shipping OUTSIDE the US please add
$11.00.

Mail to:

V-Scent	
7013 Foothill Blvd.
Tujunga, CA  91042

(ALL ORDERS FILLED WITHIN 24 HOURS OF RECEIVING THEM)
Please allow 7 days for delivery.
*************************

"Androstenone" comes with a ONE MONTH MONEY-BACK GUARANTEE!  So your one-time
fee is refundable making your decision risk free!  WE GUARANTEE THAT IF YOU ARE
NOT COMPLETELY SATISFIED, JUST RETURN THE UN-USED PORTION WITHIN 30 DAYS AND WE
WILL GIVE YOU A FULL REFUND OF THE PURCHASE PRICE.
 
__________________________________________________________________
Make A Buck Or Two @ TheMail.com - Free Internet Email
Sign-up today at http://www.themail.com/ref.htm?ref=2327556