You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Steve Brewin (Created) (JIRA)" <se...@james.apache.org> on 2011/12/16 20:14:30 UTC
[jira] [Created] (JSIEVE-79) Implement a mechanism for users to
manage their Sieve scripts via SMTP
Implement a mechanism for users to manage their Sieve scripts via SMTP
----------------------------------------------------------------------
Key: JSIEVE-79
URL: https://issues.apache.org/jira/browse/JSIEVE-79
Project: JAMES jSieve
Issue Type: Improvement
Reporter: Steve Brewin
Priority: Minor
The ability to do this safely, requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JSIEVE-79) Implement a mechanism for users to
manage their Sieve scripts via SMTP
Posted by "Steve Brewin (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175350#comment-13175350 ]
Steve Brewin commented on JSIEVE-79:
------------------------------------
Get and put operations are a bare minimum. The operations defined in RFC 5804 - "ManageSieve" represent a good base set. The authentication operations are not required as the SMTP session will already be authenticated.
> Implement a mechanism for users to manage their Sieve scripts via SMTP
> ----------------------------------------------------------------------
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: JAMES jSieve
> Issue Type: Improvement
> Reporter: Steve Brewin
> Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
> Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Updated] (JSIEVE-79) Implement a mechanism for users to
manage their Sieve scripts via SMTP
Posted by "Steve Brewin (Updated) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Brewin updated JSIEVE-79:
-------------------------------
Description:
The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
Simple get and put operations should be sufficient.
was:
The ability to do this safely, requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
Simple get and put operations should be sufficient.
> Implement a mechanism for users to manage their Sieve scripts via SMTP
> ----------------------------------------------------------------------
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: JAMES jSieve
> Issue Type: Improvement
> Reporter: Steve Brewin
> Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
> Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JSIEVE-79) Implement a mechanism for users to
manage their Sieve scripts via SMTP
Posted by "Steve Brewin (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175516#comment-13175516 ]
Steve Brewin commented on JSIEVE-79:
------------------------------------
Currently James stores the sieve scripts on the file system. It reads them via a Mailet but provides no means to write them. This issue was created to provide a resolution to this restriction. It makes sense that the resolution aligns with "managesieve" so that work could be delegated to a "managesieve" server in the future, but it doesn't require one.
Using PROTOCOLS would be good for implementing a "managesieve" server in James. A few points to bare in mind however:
- The "managesieve" server does not have to be local to James
- There are very few "managesieve" clients available, so to be of practical use a means of interacting with the server from a traditional email client would be of great value.
What is needed is:
- A Java API for interfacing to a "managesieve" server, which may be local or remote
- A library implementing the API above and core "managesieve" functionality
- An SMTP adapter, which would be implemented as a Mailet, making the operations available to an authenticated email client
- The Mailet will implement the operations directly using the library above (it would be an unnecessary overhead for the Mailet to make remote calls to a local a "managesieve" server), or delegate to a remote "managesieve" server as required.
- And of course, a local PROTOCOLS based "managesieve" server to expose the functionality externally as per RFC 5804 would be great!
Neither approach makes "more sense" than the other. They are complimentary. Both would exploit the same core "managesieve" libraries and both would be really good features to add.
> Implement a mechanism for users to manage their Sieve scripts via SMTP
> ----------------------------------------------------------------------
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: JAMES jSieve
> Issue Type: Improvement
> Reporter: Steve Brewin
> Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
> Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Issue Comment Edited] (JSIEVE-79) Implement a mechanism for
users to manage their Sieve scripts via SMTP
Posted by "Steve Brewin (Issue Comment Edited) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175516#comment-13175516 ]
Steve Brewin edited comment on JSIEVE-79 at 12/23/11 6:28 PM:
--------------------------------------------------------------
Currently James stores the sieve scripts on the file system. It reads them via a Mailet but provides no means to write them. This issue was created to provide a resolution to this restriction. It makes sense that the resolution aligns with "managesieve" so that work could be delegated to a "managesieve" server in the future, but it doesn't require one.
Using PROTOCOLS would be good for implementing a "managesieve" server in James. A few points to bare in mind however:
- The "managesieve" server does not have to be local to James
- There are very few "managesieve" clients available, so to be of practical use a means of interacting with the server from a traditional email client would be of great value.
What is needed is:
- A Java API for interfacing to a "managesieve" server, which may be local or remote
- Libraries implementing the API above, one remote and one local. The local library will implement all core "managesieve" functionality
- An SMTP adapter, which will be implemented as a Mailet, making the operations available to an authenticated email client
- The Mailet will be configurable to invoke the operations directly using the local library described above (it would be an unnecessary overhead for the Mailet to make remote calls to a local a "managesieve" server), or delegate to a remote "managesieve" server using the remote libraries described above.
- And of course, a local PROTOCOLS based "managesieve" server to expose the functionality externally as per RFC 5804 would be great! It too would use the local libraries described above
Neither approach makes "more sense" than the other. They are complimentary. Both would exploit the same core "managesieve" libraries and both would be really good features to add.
was (Author: sbrewin@apache.org):
Currently James stores the sieve scripts on the file system. It reads them via a Mailet but provides no means to write them. This issue was created to provide a resolution to this restriction. It makes sense that the resolution aligns with "managesieve" so that work could be delegated to a "managesieve" server in the future, but it doesn't require one.
Using PROTOCOLS would be good for implementing a "managesieve" server in James. A few points to bare in mind however:
- The "managesieve" server does not have to be local to James
- There are very few "managesieve" clients available, so to be of practical use a means of interacting with the server from a traditional email client would be of great value.
What is needed is:
- A Java API for interfacing to a "managesieve" server, which may be local or remote
- A library implementing the API above and core "managesieve" functionality
- An SMTP adapter, which would be implemented as a Mailet, making the operations available to an authenticated email client
- The Mailet will implement the operations directly using the library above (it would be an unnecessary overhead for the Mailet to make remote calls to a local a "managesieve" server), or delegate to a remote "managesieve" server as required.
- And of course, a local PROTOCOLS based "managesieve" server to expose the functionality externally as per RFC 5804 would be great!
Neither approach makes "more sense" than the other. They are complimentary. Both would exploit the same core "managesieve" libraries and both would be really good features to add.
> Implement a mechanism for users to manage their Sieve scripts via SMTP
> ----------------------------------------------------------------------
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: JAMES jSieve
> Issue Type: Improvement
> Reporter: Steve Brewin
> Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
> Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JSIEVE-79) Implement a mechanism for users to
manage their Sieve scripts via SMTP
Posted by "Norman Maurer (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175467#comment-13175467 ]
Norman Maurer commented on JSIEVE-79:
-------------------------------------
I think it would make more sense to implement a sievemanager directly in PROTOCOLS.
https://issues.apache.org/jira/browse/PROTOCOLS-68
> Implement a mechanism for users to manage their Sieve scripts via SMTP
> ----------------------------------------------------------------------
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: JAMES jSieve
> Issue Type: Improvement
> Reporter: Steve Brewin
> Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
> Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] [Commented] (JSIEVE-79) Implement a mechanism for users to
manage their Sieve scripts via SMTP
Posted by "Norman Maurer (Commented) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JSIEVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175466#comment-13175466 ]
Norman Maurer commented on JSIEVE-79:
-------------------------------------
I think it would make more sense to implement a sievemanager directly in PROTOCOLS.
https://issues.apache.org/jira/browse/PROTOCOLS-68
> Implement a mechanism for users to manage their Sieve scripts via SMTP
> ----------------------------------------------------------------------
>
> Key: JSIEVE-79
> URL: https://issues.apache.org/jira/browse/JSIEVE-79
> Project: JAMES jSieve
> Issue Type: Improvement
> Reporter: Steve Brewin
> Priority: Minor
>
> The ability to do this safely requires the security of an authenticated SMTP session, but if this exists why not use it to allow users to manage their Sieve scripts by mail?
> Simple get and put operations should be sufficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org