I did it by stopping the POP3 and IMAP4 services
(ControlPanel|Services... set both to Manual... restart machine). I
disabled non-SSL by setting the "Force SSL" option.
Result = SSL-based web messaging is the only way for users to
read/send mail.
Gordon
-----
Virtual Web Servers wrote:
>
> A little off topic:
>
> Are you saying that you have disabled POP3 to the mailboxes but that web
> messaging still works? Did you do this by stopping the POP3 service as a
> whole, or by user?
>
> I am trying to clarify because this would be VERY handy.
>
> Otherwise, your code looks like a good place to start.
>
> rusty
> ----- Original Message -----
> From: Gordon Williams <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, May 19, 2000 9:53 AM
> Subject: [IMail Forum] Blocking ALL attachments
>
> While I realize that most IMail administrators may not want to block
> ALL attachments coming in from outside mail domains, I'm in a
> situation where clinical & medical records are at risk (two
> departments)... warranting more decisive measures to protect the
> integrity of email and other files.
>
> As background, I've disabled POP3, IMAP4, and non-SSL web messaging
> (from day one). All I allow is SSL-based web messaging (because of
> the security needed for clinical & medical information).
>
> As of this morning, I am using the following rules to attempt to
> block ALL *incoming* attachments (has no effect on messages sent
> within the IMail domain):
>
> B~attachment; fil$ename=:trapped
> B~application/.*; nam$e=:trapped
> B~multipart/mix$ed;:trapped
> B~s/mime cryptographic sig$nature:trapped
> B~x-ms-att$achment:trapped
> B~text/x-vca$rd;:trapped
>
> NOTE - remove each instance of "$" from each of the rules before
> implementing them on your IMail system.
>
> If you prefer to delete such messages rather than send them to the
> TRAPPED mailbox, replace "trapped" with "nul" (no quotes).
>
> ??? Comments ??? -- I would appreciate any feedback about these
> rules. I believe the syntax is correct in each instance. I'd also
> welcome other suggestions of rules WHEN the objective is to filter
> all *incoming* messages with attachments.
>
> I'm not particularly interested in a debate about whether I *should*
> be filtering all attachments. That's to be debated and decided on a
> domain-by-domain basis, given the context within which you are
> operating (my context briefly described above).
>
> For those few of you who may wish to block all incoming attachments,
> hopefully the rules above will give you a jump-start on the
> challenge.
>
> To Ipswitch developers -- It would be nice if you would find another
> delimiter besides ":" so that the filter text itself could match on
> a string like this:
>
> Content-Disposition: attachment;
>
> where ":" is part of the match string itself. The colon (:) is a
> very common character associated with headers and attachments. It
> seems a shame to preclude our using it as part of the match string.
>
> It would also be nice (necessary) for the rules to work on messages
> sent within the IMail domain (from one account to others inside the
> domain).
>
> Gordon Williams
> Michigan State University
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
