Hi Yannick,
Unfortunately I don't think we will have DSN for september.
Maybe mid-2007 have much more probability.
I think it would be easy to implement the protocol but currently there
is no way to give informations on a per recipient basis at the end of
the DATA reply because James does queue the message and does not know if
a recipient have problem and another not.
From what I understood from LMTP rfc that feature is the cause LMTP has
been created so I don't see the point of supporting the LMTP protocol if
we are not able to give this feature.
Supporting LMTP would be otherwise simple:
1) create a new package like smtpserver (lmtpserver)
2) create an LHLOCmdHandler that simply extends EHLOCmdHandler from the
smtp package
3) create an extension of the DataCmdHandler (LmtpDataCmdHandler) to
return one result line for each recipient.
4) create a default configuration of the handlerchain including the
needed commands (LhloCmdHandler, MailCmdHandler, RcptCmdHandler,
LmtpDataCmdHandler, QuitCmdHandler)
Stefano
yannick quenec'hdu wrote:
Stephano,
Thank you for this information. Think of implementing DSN in James
quickly ?
If not, I think that I can make a hack in James to integrate this option
and
to validate conformity with protocle LMTP.
I could do it in September, planned something on you side ?
Best Regards
Yannick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
