Clarence,
Sorry -- I have to disagree with you again.
It is *NOT* "a new convention." IIRC, I was the first to notice that
extensions were not being appended, but it appeared to be only for EXE
extensions; *I* said that was a cool security measure. Only after I
said that did xChaos jump in to say "It's not a bug, it's a feature."
Well, IT'S A BUG!!
If what you said were actually the case, that the extension has to be in
MIME.CFG, that could be a feature. But that is NOT the case. Believe
me, JPG is an "approved extension" in my mime.cfg file ... and it was
JPG files I spend the other day fighting with.
For awhile I thought the problem might be related to LFN, but double
checking and renaming files to 8+3 in the original mail did *not* solve
the problem.
l.d.
====
On Mon, 16 Apr 2001 16:58:36 -0500, Clarence Verge wrote:
> L.D. Best wrote:
>> Has anyone even bothered to figure out why sometimes the extension makes
>> it to the unattached file, and sometimes it doesn't???
> There is a new convention in place for security purposes (which I don't
> much like) that results in downloaded files and attachments having NO
> extension appended UNLESS it is in the list of approved extensions in
> MIME.cfg.
> The section that says: "I will save these with the proper extension".
> I'm not a big security fan, and I already know that most users don't like
> to tinker with mime.cfg - so this is obviously gonna be a problem.
> - Clarence Verge
> --
> - Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
> - The internet is infected - Windows is a VIRUS !!
> --
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
