From: Pavel@Janik.cz (Pavel Janík)
Cc: ding@gnus.org
Subject: Re: Large *.pif base64 attachments and Gnus...
Date: 03 Aug 2001 09:19:43 +0200 [thread overview]
Message-ID: <m3wv4lmwz4.fsf@SnowWhite.SuSE.cz> (raw)
In-Reply-To: <ylitg6yn7u.fsf@windlord.stanford.edu>
From: Russ Allbery <rra@stanford.edu>
Date: 02 Aug 2001 17:57:25 -0700
Hi,
> > you probably see the same behaviour of our Outlook colleges sending us
> > big .doc.pif files ;-) I'm trying to save them to a file with `o' on the
> > MIME button.
>
> This is almost certainly the SirCam virus, just so that you know.
> (There's very rarely any reason for anyone to send you a .pif file; .pif
> is the extension for a control file specifying how to run a DOS program
> under Windows, IIRC.) The .doc.pif bit in particular gives this away as
> SirCam.
of course I know this is SirCam. See the `;-)' at the end of sentence. The
thing I'm trying to solve on the list of Gnus developers is to fix the
apparent bug in Gnus which saves an article as plain base64 bytes without
decoding... Just try it yourself and tell me, if it works for you. I;d like
to really SEE the contents of the file they sent me...
--
Pavel Janík
Be warned: emacs has a steep upward learning curve.
-- a.l.meyers@consult-meyers.com in gnu.emacs.help
next prev parent reply other threads:[~2001-08-03 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 23:10 Pavel Janík
2001-08-03 0:57 ` Russ Allbery
2001-08-03 7:19 ` Pavel Janík [this message]
2001-08-04 15:51 ` Florian Weimer
2001-08-04 19:58 ` Pavel Janík
2001-08-04 23:36 ` Simon Josefsson
2001-08-05 7:42 ` Florian Weimer
2001-08-05 9:11 ` Pavel Janík
2001-08-09 19:36 ` Simon Josefsson
2001-08-10 14:57 ` Florian Weimer
2001-08-11 22:12 ` Simon Josefsson
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=m3wv4lmwz4.fsf@SnowWhite.SuSE.cz \
--to=pavel@janik.cz \
--cc=ding@gnus.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).