[ https://issues.apache.org/jira/browse/JAMES-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3867. --------------------------------- Resolution: Fixed > Make IMAP modular > ----------------- > > Key: JAMES-3867 > URL: https://issues.apache.org/jira/browse/JAMES-3867 > Project: James Server > Issue Type: Improvement > Components: guice, IMAPServer > Reporter: Benoit Tellier > Priority: Major > Fix For: 3.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > As an IMAP administrator I want to customize IMAP processing easily. This > includes removing/adding/changing IMAP processors/encoders/decoders. > This allows the following use cases: > - Add support for (potentially custom) IMAP extensions without recompiling > James > - Removing support for buggy commands easily, if any > - Enforcing "read only behaviour" > - Customizing some commands. For instance one of my customers got a tricky > non standard IMAP authenticate command to handle. > The admin would specify a list of ImapPackage (which is itself a bundle of > processors/encoders/decoders) from the imapserver.xml configuration file. By > default, if unspecified the default IMAP package would be used. > Both ImapPackage/processors/encoders/decoders loading would leverage the > extensions-jars mechanism. > h3. Definition of done > Write an exemple of such modularization writing a PING / PONG command and > load it into a James server. > {code:java} > A001 PING whatever > * PONG whatever > A001 OK PING command completed. > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org