On Sat, 16 Jul 2005, Jem Berkes wrote:
I want to focus a bit on mod_smtpd design, in particular the protocol
module (which accepts connections and does the E/SMTP talking). I've seen
various ideas thrown around on what exactly the module should do. It would
be nice if we could come up with at
Jem Berkes [EMAIL PROTECTED] writes:
The competing technology seems to be Sendmail's milter
interface which allows developers to hook their custom
filters into various stages of SMTP transactions.
If you follow the design of httpd, then you want to create
an smtp_in filter that removes any
I want to focus a bit on mod_smtpd design, in particular the protocol
module (which accepts connections and does the E/SMTP talking). I've seen
various ideas thrown around on what exactly the module should do. It would
be nice if we could come up with at least the high level design specs for
Jem Berkes [EMAIL PROTECTED] writes:
I think this granularity is required. But I'm not
sure about how the DATA hook would work?
Have you considered using libapreq2 for parsing
the mime headers in there? The header parser
should really convenient for that, you could
even introduce a
Joe Schaefer [EMAIL PROTECTED] writes:
Jem Berkes [EMAIL PROTECTED] writes:
I think this granularity is required. But I'm not
sure about how the DATA hook would work?
Have you considered using libapreq2 for parsing
the mime headers in there? The header parser
should really convenient
Have you considered using libapreq2 for parsing
the mime headers in there? The header parser
should really convenient for that, you could
even introduce a post-header-parser hook that
runs when the parser finishes.
My own suggestion is that we don't touch or try to interpret MIME. Parsing
Jem Berkes [EMAIL PROTECTED] writes:
Have you considered using libapreq2 for parsing
the mime headers in there? The header parser
should really convenient for that, you could
even introduce a post-header-parser hook that
runs when the parser finishes.
My own suggestion is that we don't
