Actually you can have multiple milter processes if you want, but
MimeDefang handles about everything. Also, sendmail has separate
conversations with the milter(s) for each operation which
MimeDefang might hand off to different slaves. The side effect
is that you don't block on some other long-running process unless
you are out of slaves but you also can't count on globals that
you set in one step (checking the sender or recipients) to be
available in later steps - but MimeDefang passes most of the
information you need each time and has dropped a complete
copy of the message broken out into its MIME components in
files where the programs can find them (hence the name and
the advantage of running multiple scanners under its control).
So you are saying that mimedefang is not reliable if not provided enough
resources.
No, I didn't say anything even close to suggesting that - and I'm
curious as to why you imagined I did. What I said was that different
phases of the filtering are likely to be handled in different processes
so your programming should be done accordingly.
Well, I did not quite get your 'can't count on globals' which you put
after 'unless you are out of slaves'. That gave the impression that
something was not on if you run out of resources. Are the globals you
talk about ones you set or sendmail sets?
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
