From: dme@dme.org (David Edmondson)
Cc: ding@gnus.org
Subject: Re: Gnus + procmail question
Date: Wed, 24 Sep 2003 08:10:10 +0100 [thread overview]
Message-ID: <m2brtamzl9.fsf@chocolate-chip-cookie.dme.org> (raw)
In-Reply-To: <vuobrtbs744.fsf@csa.bu.edu>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
* emerick@cs.bu.edu [2003-09-23 19:16:27]
> I'm using procmail to pre-filter my e-mail so that anything with a
> dangerous-looking attachment (.exe, .pif, etc.) gets forwarded to
> /dev/null (everything else stays in my spool). Given that this is the
> only way I'm using procmail, do I have to tell Gnus about it at all?
No.
[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]
next prev parent reply other threads:[~2003-09-24 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 18:16 Emerick Rogul
2003-09-24 7:10 ` David Edmondson [this message]
2003-09-24 10:26 ` Ted Zlatanov
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=m2brtamzl9.fsf@chocolate-chip-cookie.dme.org \
--to=dme@dme.org \
--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).