Hi all,
I would like to know you opinion about the following.
I am getting a "Segmentation fault(coredump)" when processing a mail archive
with mhonarc. The command is basically:
mhonarc -quiet -rcfile /sth/uala_frames.mrc -outdir /sth /sth/mailfolder
about the resource file. I am pretty sure it is right. It is the same I am
using since long.
I cat the "mailfolder" in single mails and I did:
mhonarc -single -rcfile /sth/uala_frames.mrc < msg0001 > msg0001.html
And I could process all the messages but one. Now I don't know what to do to
avoid it apart from erasing it. I am running on Solaris 5.6, perl version
5.005_04 and mhonarc v2.4.5
Part of the message is as follows:
This is a multi-part message in MIME format.
------=_NextPart_000_00F1_01C20BB6.4D1F1030
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
FYI
------=_NextPart_000_00F1_01C20BB6.4D1F1030
Content-Type: text/html;
name="FOCUS AGENDA 26.htm"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="FOCUS AGENDA 26.htm"
<BASE =
HREF=3D"http://meetings/FOCUS/private/focus26.htm";>=0A=
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office"=0A=
xmlns:w=3D"urn:schemas-microsoft-com:office:word"=0A=
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"=0A=
xmlns=3D"http://www.w3.org/TR/REC-html40";>=0A=
=0A=
<head>=0A=
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">=0A=
<meta name=3DProgId content=3DWord.Document>=0A=
<meta name=3DGenerator content=3D"Microsoft Word 9">=0A=
<meta name=3DOriginator content=3D"Microsoft Word 9">=0A=
<link rel=3DFile-List href=3D"./focus26_files/filelist.xml">=0A=
<title>FOCUS AGENDA 26</title>=0A=
<!--[if gte mso 9]><xml>=0A=
<o:DocumentProperties>=0A=
<o:Author>cattaneo</o:Author>=0A=
<o:Template>FOCUS_Agenda</o:Template>=0A=
<o:LastAuthor>boucrot</o:LastAuthor>=0A=
<o:Revision>2</o:Revision>=0A=
<o:TotalTime>50</o:TotalTime>=0A=
<o:LastPrinted>2002-06-04T06:33:00Z</o:LastPrinted>=0A=
<o:Created>2002-06-04T06:33:00Z</o:Created>=0A=
....
Do you know which are the characters producing this kind of error in mhonarc,
or which are the limitations processing MIME parts?
Thanks a lot.
Ruben
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-USERS
