Always looking for good procmail recipes I couldn't resist this one from
Chuck. However, when I cut and pasted it into my procmailrc file it
generated lots of errors but to my great surprise it actually worked.
If you check out what word wrapping did you will easily see why it had
problems. The
On Mon, 5 Feb 2001, Enrico Payne wrote:
> So, to those who value their own privacy, while on company
> time and company property (including PC's and Internet
> access), Bah. If I can reduce the risk of future exposure
> to viruses by blocking or deleting attachments that could
> contain viruses,
On Mon, 05 Feb 2001 14:08:10 Enrico Payne wrote:
[snip]
>Having said that, I too am a reasonable person, and understand that not all
>attachments are dangerous. Hence I would only prevent file types that could
>be launched by the browser, e-mail, or just by double clicking on it.
>Chuck's solution
e types that could
be launched by the browser, e-mail, or just by double clicking on it.
Chuck's solution is a good compromise! :->
Thanks for the thoughts
Regards
Enrico
- Original Message -
From: "Mike Burger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
S
Yup...very lucky.
On Mon, 5 Feb 2001, Vidiot wrote:
> >So, tell me...how many emails have you received with VB scripts and
> >ActiveX components that were real emails, vs. the bogus crap that has been
> >passing through the net for the last few months?
>
> I don't receive any e-mail that contain
>So, tell me...how many emails have you received with VB scripts and
>ActiveX components that were real emails, vs. the bogus crap that has been
>passing through the net for the last few months?
I don't receive any e-mail that contains those attachments. All of
my e-mail reading and sending is d
Fine and dandy if there is A) an available virus scanner and B) it
properly scans for, detects and fixes said problems.
So, tell me...how many emails have you received with VB scripts and
ActiveX components that were real emails, vs. the bogus crap that has been
passing through the net for the la
On Mon, 5 Feb 2001, Vidiot spewed into the bitstream:
V>>I need to do the following with my e-mail server...
V>>
V>>a) Block all e-mails that have .exe, .vbx, .ocx extensions
V>
V>Why? None of those extensions affect Linux/Unix boxes.
Maybe he's got Windoze clients using his machine as their
>In business situations, email is a tool, provided by the employer, to be
>used as the employer decides is appropriate. As such, the employer also
>gets to determine the type of email that enters/exits that mail system.
Instead of globally deep-sixing said extension, companies filter (ours does)
On Mon, 5 Feb 2001, Vidiot wrote:
> >I need to do the following with my e-mail server...
> >
> >a) Block all e-mails that have .exe, .vbx, .ocx extensions
>
> Why? None of those extensions affect Linux/Unix boxes. Also, not all
> e-mail that has those extension is bad. Deep-sixing said e-mail
>I need to do the following with my e-mail server...
>
>a) Block all e-mails that have .exe, .vbx, .ocx extensions
Why? None of those extensions affect Linux/Unix boxes. Also, not all
e-mail that has those extension is bad. Deep-sixing said e-mail in general is
a bad idea.
Plus, you have to a
On Mon, 5 Feb 2001, Enrico Payne spewed into the bitstream:
EP>I need to do the following with my e-mail server...
EP>
EP>a) Block all e-mails that have .exe, .vbx, .ocx extensions
Put this in /etc/procmailrc
:0
*^Content-type: (multipart/mixed|application/octet-stream)
{
:0 HB
*^Conten
I need to do the following with my e-mail server...
a) Block all e-mails that have .exe, .vbx, .ocx extensions
b) Put in a footer (disclaimer) on all e-mails sent from the server.
I currently use sendmail 8.9.3, but do not know how to write the necessary
recipes to do these things. I looked at s
13 matches
Mail list logo
