Has anyone ran across a issue while running amrecover where the file that is
requested and extracted from recover is not at all the file you ended up
with. The filename/extension are correct but the actual content is not at
all what the original was. So to illustrate what I am trying to say here is
my example....

I was expecting the following output in my recovered text file;

14grand:$1$FUP5cjOh$mEfi4gAXrCq5xOyY.Y4tH/:1:0:14grand:/usr/local/vpopmail/d
omai
ns/**/14grand:16000000S
17706303:$1$Nc1pDv1T$h.zl9f.NyjJgCBgasdQZr1:1:0:17706303:/usr/local/vpopmail
/dom
ains/**/17706303:16000000S
1974bliss:$1$BsFFyTES$EiyfprX/JMGNf756ZayDl.:1:0:1974bliss:/usr/local/vpopma
il/d
omains/**/1974bliss:16000000S
1andonly:$1$L7luiB5y$n4XW5ATnp1.llKowR9bRZ1:1:0:1andonly:/usr/local/vpopmail
/dom
ains/**/1andonly:16000000S


But I got this instead;

Return-Path: <info@**>
Delivered-To: 21stcentury@**
Received: (qmail 42535 invoked by uid 0); 1 Feb 2005 18:00:59 -0000
Received: from unknown (HELO**
  by zeata.interlinc.net with SMTP; 1 Feb 2005 18:00:59 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----_=_NextPart_001_01C43209.B50370E0"
Subject: Interlinc.net Billing Reminder
Date: Tue, 01 Feb 2005 18:14:25 GMT
From: <info@**>
To: <21stcentury@**>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C43209.B50370E0
Content-Type: text/plain;
        charset="us-ascii"

Etc etc etc etc


So as you can see I was expecting a bunch of text garbage but got an email
instead... LOL

Any insight on what I could have done wrong?


Thanks in advance,
Jason