Hi all, Hi Todd,

preface:

today I had a meeting with one of my clients, who needs a solution to give
internet/intranet access to about 100 workplaces. Just the "standard" thing,
some will get mail, some will have intranet access to "company documents",
some will be allowed to have access to the internet.

it looks like sambar will be a solution for some parts (and it fitts into
the existing infrastructure).


the problem:

They need special security features for email. certain attachments have to
be forbidden or allowed etc. this can not be done by a simple extention rule
system (f.x. "no doc-files), it has to be done on a content level.

Part of my job will be to ensure this.

Current idea is to write a small application that parses the email, analyzes
the content and applies the rules.


the feature request:

idea A.)

A standard filter mechanism: sambar calls an executable and passes
parameters to access a certain file containing the mail. Or sambar pipes out
the mail content and expects the answer to be piped in into sambar.

This would give a problem with high mail loads due to the fact, that the
program needs to be loaded for every mail. And the program has to read its
settings etc etc.


idea B.)

sambar places all fetched and received mail into a certain folder or folder
structure (folder structure will be easier, i think) and does NO processing.

my programm will process the mail and after processing the mail, it will
move the mail into a different structure where sambar will pick it up.

This would need two pollings, so mail will be delayed.


I would prefer idea a, because it sounds easier to implement for Todd. The
"high load" problem can be solved with some tricks, if it is ever needed.


Or is this feature already implemented?


Holger Lembke
+49-531-334676


--------------------------------------------------------------------------------
For unsubscription of this list send an email to [EMAIL PROTECTED] with email
data containing unsubscribe emailadd sambar

Reply via email to