On Mon, 13 May 2002, dman wrote:
> This makes sense. However, this external lib shouldn't dupliate exim
> either. In this example, serializing the message according to
> RFC2822, exim must already do this in many situations.
Yes, it has a function for doing that. But...
> I think the
> two should cooperate -- exim provide a public interface to the
> (useful) stuff it already does, and an external lib to provide other
> things that a local_scan might want. Of course, if exim's
> implementation of some feature is too tied into its own usage, then it
> may not be a good idea to try and expose a public interface to it.
... exactly. Exim's code for generating an output message is wrapped up
with the code for adding and removing header lines and passing the
message to its actual output writing functions (that do blocking and
CRLF handling, encryption, etc).
> The biggest problem with this (from my perspective) is that I don't
> know how to dynamically load modules in C. (I wouldn't be much help
> until I figured it out)
Neither do I. :-)
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
