Status: Read
Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Thu, 19 Oct 2000 13:03:45 -0400
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id MAA16156;
	Thu, 19 Oct 2000 12:58:37 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Thu, 19 Oct 2000 12:53:03 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id MAA15929
	for tiff-outgoing; Thu, 19 Oct 2000 12:53:03 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from waco2.calpha.com (root@waco2.calpha.com [208.232.233.3])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id MAA15926
	for <tiff@olympiakos.com>; Thu, 19 Oct 2000 12:53:00 -0400
Received: from apexinternetsoftware.com (63-80-24-025.calpha.com [63.80.24.25])
	by waco2.calpha.com (8.9.3/8.9.3) with ESMTP id LAA14533;
	Thu, 19 Oct 2000 11:52:52 -0500
Message-ID: <39EF291D.B86CA1D5@apexinternetsoftware.com>
Date: Thu, 19 Oct 2000 13:02:22 -0400
From: Andy <apex@apexinternetsoftware.com>
Organization: Apex Internet Software
X-Mailer: Mozilla 4.08 [en] (Win98; U)
MIME-Version: 1.0
To: Howard Kaikow <kaikow@standards.com>, tiff@olympiakos.com
Subject: Re: Attachments sent to list
References: <4.3.2.7.0.20001019110709.00b03dd8@pop3.norton.antivirus> <4.3.2.7.0.20001019113804.00b15068@pop3.norton.antivirus>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@olympiakos.com

Hi Howard, libtiff,

Heh, it was almost in jest.  I agree with you that the cards or signatures (often
invalidated by list remailer) and redundant rich media reformats of the relevant
information are chaff, and more or less simply deleted.

Most posts to most mailing lists, generally, are free of these details, with
posters posting only ASCII with URLs.

I have seen perhaps three to ten times where viruses have been sent through
mailing lists, they're pretty obvious to the relatively more sophisticated
mailing list users, and often innocuous to varying software vendor
implementations.

So I agree that mailing list posts should be regular text only messages.

Attachments of documents or examples or files sometimes happen, often it's
convenient when most of the list's users are expecting or will review the
document, or otherwise expect it.

Some mailreaders give those that receive rich media e-mail many lines of base64
and/or MIME chaff, they can delete as easily as anyone else, or moreso.

I think attached text only files are generally OK, but that is my interpretation.

So, that is one reader's opinion.

Basically, there is no enforcement besides banning upon list administrator pique
(never happens) or total public castigation (never happens), because noone ever
sends malicious e-mails to the mailing lists.  Some might argue that, there are
plenty of arguments.

Some list server software has ways to manage output to the list.

As an obligatory libtiff comment, making a generalized OJPEG reader to handle the
five+ common OJPEG implementations would be quite a hassle.  It might be better
to have a more specialized ojtiftojtif program, and maybe then even jtiftoojtif.

Andy



Howard Kaikow wrote:

> I should hope, also:
>
>  >>         1. Those containing contact info, such as .vcf or winmail.dat
> files,
>  >>         2. Those containing a copy of the message, often as an HTML file.
>
> At 11:37 10/19/2000, Andy wrote:
>  >The following attachment types are discouraged:
>  >
>  >1.  Virus
>  >2.  File greater than 25 kilobytes, without alternate arrangement,
> depending on
>  >the list and its audience.
>  >
>  >;)
>  >
>  >Howard Kaikow wrote:
>  >
>  >> There needs to be an established policy whether it is OK to send
>  >> attachments to this list.
>  >> In particular, I would suggest that the following types of attachments be
>  >> discouraged:
>  >>
>  >>         1. Those containing contact info, such as .vcf or winmail.dat
> files,
>  >>         2. Those containing a copy of the message, often as an HTML file.
>  >
>  >--
>  >contact Andy
>  >company Apex Internet Software
>  >email info@apexinternetsoftware.com
>  >website http://www.apexinternetsoftware.com/

--
contact Andy
company Apex Internet Software
email info@apexinternetsoftware.com
website http://www.apexinternetsoftware.com/


