[
https://issues.apache.org/jira/browse/JAMES-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3574.
---------------------------------
Resolution: Fixed
The pull request did contribute this.
> As a LMTP user I want to execute the mailet container
> -----------------------------------------------------
>
> Key: JAMES-3574
> URL: https://issues.apache.org/jira/browse/JAMES-3574
> Project: James Server
> Issue Type: Improvement
> Components: lmtp, MailStore & MailRepository
> Affects Versions: 3.6.0
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> h3. Why?
> LMTP is SMTP without a mail queue. Used inside a private network, with
> trusted hosts, the throughput is controlled upstream by the MTA/MX servers.
> There is no sudden burst requiring buffering - buffering is done upstream.
> James ships a LMTP implementation that mostly reuses the SMTP stack.
> Today it delivers emails directly in people mailboxes.
> The mailet container allows a declarative, modular and extensible processing
> upon email reception and is one of James selling points. Sadly today LMTP
> users cannot leverage its power...
> h3. How?
> Write a `DataLineMessageHookHandler` that given an incoming LMTP transaction
> executes the mailet container.
> Write a handler chain mirroring the default one, replacing the classical
> `DataLineMessageHookHandler` with the one executing the mailet container.
> Write a unit test showing that upon an incoming LMTP transaction the mail is
> executed by a mock of the Mailet Container.
> Finally write documentation concerning the handler chain.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
