Path: number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.adelphia.com!news.adelphia.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 08 Jan 2006 04:08:57 -0600
Newsgroups: fidonet.bluewave
From: William_McBrine@f2000.n106.z1
Date: Sat, 07 Jan 2006 21:48:52 -0500
Subject: Re: Do not give up nor down.
Message-ID: 
References: 
Organization: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671
 130/803
 21 1414
Lines: 22
NNTP-Posting-Host: 24.54.66.112
 properly
Xref: number1.nntp.dca.giganews.com fidonet.bluewave:24

-=> JEAN PARROT wrote to JOHNJWILSON <=-

 JP> Look at the suffix of your D/L'd packet, it will tell you a story. 
 JP> Find out what file your MM will "see". Try and change that suffix then 
 JP> from .xxx to .yyy. Might work, no promise.

No, MultiMail doesn't determine the packet type based on the filename 
extension. Rather, it examines the first few bytes of the file; from that, 
it determines the archive type; extracts with the appropriate archiver; and 
looks at the resulting files to determine the packet type.

So, if the unarchiving step failed, but MultiMail didn't get an error code 
from the archiver, it used to give the "Packet type not recognized" 
message. But since version 0.42, after extracting, it checks to see if 
there are any files present; if not, it says "No files uncompressed - check 
archiver config".

So I don't know why someone might see this message today, unless it's 
really not one of the supported packet types (QWK/Blue Wave/etc.), or 
they're using an old version of MultiMail. Or there's a bug...

.. ///\oo/\\\ Bugs? What bugs? ///\oo/\\\ ///\oo/\\\