linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jens Knoell" <jens@ing.twinwave.net>
To: Linux Admin ML <linux-admin@vger.kernel.org>
Subject: metamail and klez...
Date: Tue, 30 Apr 2002 01:04:30 -0600	[thread overview]
Message-ID: <004301c1f015$4b86cef0$0264a8c0@wombie> (raw)

I've got an interesting problem:

My mail filter uses metamail to break incoming mail apart and look into
possibly dangerous attachments. It does fail for Klez-infected eMails, and I
am a little at a loss how to fix it:
------<snip>-----
> metamail -w -x infected.eml
Date: Tue, 30 Apr 2002 07:38:25 +0200 (MET DST)
From: info <info@eib.org>
To: jens@ing.twinwave.net
Subject: CELLPADDING

Ignoring unparsable content-type parameter: ''
Cannot handle any part of multipart/alternative message
-----</snip>-----

Any idea why it's puking on it, and how to get to the two attachments?

Jens


             reply	other threads:[~2002-04-30  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30  7:04 Jens Knoell [this message]
2002-04-30  7:37 ` metamail and klez Horia Chirculescu
2002-04-30 10:00 ` Scott Taylor
2002-04-30 10:20   ` Nicolas Costes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004301c1f015$4b86cef0$0264a8c0@wombie' \
    --to=jens@ing.twinwave.net \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).