Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
experimentalmodules:imaproadmap [2007/01/24 09:39] sbernheartexperimentalmodules:imaproadmap [2008/02/08 19:49] (current) – external edit 127.0.0.1
Line 21: Line 21:
   - alter the pop3/NNTP proxies to honor the per-bucket IMAP assignment by sending the real message via the move_message function (possibly moved to a seperate module??) and then pass a pre-generated stub message to the client   - alter the pop3/NNTP proxies to honor the per-bucket IMAP assignment by sending the real message via the move_message function (possibly moved to a seperate module??) and then pass a pre-generated stub message to the client
   - add additional delivery options to move_message (SMTP, LMTP, NNTP post, local files in various formats, etc)   - add additional delivery options to move_message (SMTP, LMTP, NNTP post, local files in various formats, etc)
-  - add additional non-IMAP message source options (POP3 'fetchmail' option as well as the proxy option, SMTP listener, etc) these sources would retreive the messages and then classify them and deliver them via move_message+  - add additional non-IMAP message source options (POP3 'fetchmail' option as well as the proxy option, SMTP listener, etc) these sources would retrieve the messages and then classify them and deliver them via move_message
  
 Thoughts? As long as this is, I know I've left something out (I have remembered it a half a dozen times as I was typing something else, only to forget it before I finished what I was doing) not to mention things that I have never considered. Thoughts? As long as this is, I know I've left something out (I have remembered it a half a dozen times as I was typing something else, only to forget it before I finished what I was doing) not to mention things that I have never considered.
Line 27: Line 27:
 This roadmap ends up morphing popfile into a swiss-army-knife classifier. This roadmap ends up morphing popfile into a swiss-army-knife classifier.
  
-I start off with tiny concrete steps that are valuble in of themselves, but they also build towards the possibility of implementing the later items fairly easily. Some of the later options are much more general and I don't know how necessary they really will be. Some of them are as much for overall consistancy as anythng else (if you say that bucket spam should go to this place, it really should go there, no matter if the source of that spam is via POP3, IMAP, or SMTP).+I start off with tiny concrete steps that are valuble in of themselves, but they also build towards the possibility of implementing the later items fairly easily. Some of the later options are much more general and I don't know how necessary they really will be. Some of them are as much for overall consistancy as anything else (if you say that bucket spam should go to this place, it really should go there, no matter if the source of that spam is via POP3, IMAP, or SMTP).
  
 At the moment, popfile is a POP3 proxy that has IMAP bolted onto the side. I haven't seen the info on how the SMTP and NNTP stuff will work so I don't know how well they are really integrated, but I think these steps will integrate the IMAP support in nicely and end up opening up a lot of new possibilities. At the moment, popfile is a POP3 proxy that has IMAP bolted onto the side. I haven't seen the info on how the SMTP and NNTP stuff will work so I don't know how well they are really integrated, but I think these steps will integrate the IMAP support in nicely and end up opening up a lot of new possibilities.
 
experimentalmodules/imaproadmap.1169631588.txt.gz · Last modified: 2008/02/08 19:49 (external edit)
Old revisions

Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.

Recent changes RSS feed Donate Driven by DokuWiki
The content of this wiki is protected by the GNU Fee Documentation License