Return-Path: Sender: "Marvin Kaye" To: lml@lancaironline.net Date: Sun, 26 Sep 2004 20:48:03 -0400 Message-ID: X-Original-Return-Path: Received: from imo-m23.mx.aol.com ([64.12.137.4] verified) by logan.com (CommuniGate Pro SMTP 4.2.3) with ESMTP id 433326 for lml@lancaironline.net; Sun, 26 Sep 2004 20:41:03 -0400 Received-SPF: pass receiver=logan.com; client-ip=64.12.137.4; envelope-from=Sky2high@aol.com Received: from Sky2high@aol.com by imo-m23.mx.aol.com (mail_out_v37_r3.7.) id q.1e3.2bb5839e (2519) for ; Sun, 26 Sep 2004 20:40:25 -0400 (EDT) From: Sky2high@aol.com X-Original-Message-ID: <1e3.2bb5839e.2e88bb78@aol.com> X-Original-Date: Sun, 26 Sep 2004 20:40:24 EDT Subject: Help!! Lancair Mail List information lost in the bowels of ? X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1096245624" X-Mailer: 9.0 for Windows sub 5000 -------------------------------1096245624 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Although interestng, many recent posts contain neither aircraft indentification, questioner's citation, or the name of the responder. Here's the problem: 1. A topic thread search is useless. 2. Expert responders (and lurkers) have no idea as to what aircraft is involved. 3. Without a Name, aircraft type or engine info, any response is blind, mis-directed or ????. 4. Instead of appearing stupid, the message is often ignored by a potential responder. How about trying to adhere to the following format: 1. If asking for information, try to include the aircraft type in the "Subject" or at least in the text. 2. Try to provide complete information in the query - type, fast/slow build, custom details, etc. The intro can be useful since we are learning things like "Salutti Tutti" and "G'day mate" are source country identifiers. More info is better. 3. Sign the text with your name, aircraft, engine id and location (airport or city). When replying, pleeeeeease: 1. If your browser allows, copy the material to which you are replying. 2. Reply to the person by name (it's more friendly). 3. If you can't do item #1, please provide some context. 4. Sign the text with your name, aircraft, engine id, location (airport or city) and maybe even country. If you have a problem with complying, it's no problem - I guess we'll just continue to founder along. Scott Krueger AKA Grayhawk N92EX IO320 Aurora, IL (KARR), USA, Planet Earth, Solar System as we know it. PS: In the old days, before sending a communique to our overseas subsidiaries or agents, I frequently got up and moved to the other side of my desk and tried to read the transmission as though I had no prior information. This frequently resulted in some editing to establish the context within which the information would be useful. Try it next time, before you hit the "send" function. It's so much more efficient. -------------------------------1096245624 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Although interestng, many recent posts contain neither aircraft=20 indentification, questioner's citation, or the name of the responder.

Here's the problem:

1. A topic thread search is useless.

2. Expert responders (and lurkers) have no idea as to what aircraf= t is=20 involved.

3. Without a Name, aircraft type or engine info, any response is blind,= =20 mis-directed or ????.

4. Instead of appearing stupid, the message is often ignored by a= =20 potential responder.

How about trying to adhere to the following format:

1. If asking for information, try to include the aircraft type in= the=20 "Subject" or at least in the text.

2. Try to provide complete information in the query - type, fast/= slow=20 build, custom details, etc. The intro can be useful since we are learn= ing=20 things like "Salutti Tutti" and "G'day mate" are source country=20 identifiers. More info is better.

3. Sign the text with your name, aircraft, engine id=20 and location (airport or city).

When replying, pleeeeeease:

1. If your browser allows, copy the material to which you ar= e=20 replying.

2. Reply to the person by name (it's more friendly).

3. If you can't do item #1, please provide some context.

4. Sign the text with your name, aircraft, engine id, location (airport= or=20 city) and maybe even country.

If you have a problem with complying, it's no problem - I guess we= 'll=20 just continue to founder along.

Scott Krueger=20 AKA Grayhawk
N92EX IO320 Aurora, IL (KARR), USA, Planet Earth, Solar Syst= em=20 as we know it.

PS: In the old days, before sending a communique to our over= seas=20 subsidiaries or agents, I frequently got up and moved to the other side of m= y=20 desk and tried to read the transmission as though I had no prior=20 information. This frequently resulted in some editing to establish the= =20 context within which the information would be useful. Try it next time= ,=20 before you hit the "send" function. It's so much more=20 efficient.

-------------------------------1096245624--