This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
experimentalmodules:imapinstructions [2007/01/23 11:49] – manni | experimentalmodules:imapinstructions [2007/11/13 12:08] – manni | ||
---|---|---|---|
Line 4: | Line 4: | ||
===== What IMAP.pm does (or tries to do) ===== | ===== What IMAP.pm does (or tries to do) ===== | ||
- | IMAP.pm, unlike | + | |
+ | IMAP.pm, unlike POPFile' | ||
IMAP.pm not only checks for new incoming mail, it also scans its output folders for mail that you moved there. For example, if you have created IMAP folders " | IMAP.pm not only checks for new incoming mail, it also scans its output folders for mail that you moved there. For example, if you have created IMAP folders " | ||
+ | |||
To summarize: | To summarize: | ||
* IMAP.pm will try to classify new messages and move them accordingly | * IMAP.pm will try to classify new messages and move them accordingly | ||
Line 11: | Line 14: | ||
===== What IMAP.pm (currently? | ===== What IMAP.pm (currently? | ||
+ | |||
* It cannot talk to multiple IMAP servers. | * It cannot talk to multiple IMAP servers. | ||
* It will not modify the subject (according to classification) or add any of the X-POPFile-Link or X-Text-Classification headers to messages. | * It will not modify the subject (according to classification) or add any of the X-POPFile-Link or X-Text-Classification headers to messages. | ||
Line 17: | Line 21: | ||
===== What you need to run IMAP.pm ===== | ===== What you need to run IMAP.pm ===== | ||
- | The IMAP module is not included in the default distribution of POPFile 0.22.2. A special [[http:// | + | All you need is a mail client with IMAP capabilities and an IMAP account at your ISP. The rest of the functionality is distributed along with POPFile. |
- | + | ||
- | If you are not on Windows, you can download the latest version of the IMAP module that works with POPFile 0.22.2, 0.22.3 or 0.22.4 | + | |
- | + | ||
- | If you are using the cvs version of POPFile, you should download the module [[http:// | + | |
- | + | ||
- | Of course, you will also need a mail client with IMAP capabilities and an IMAP account at your ISP. | + | |
===== How to get it running ===== | ===== How to get it running ===== | ||
IMAP.pm is disabled by default. To enable it, | IMAP.pm is disabled by default. To enable it, | ||
- | * start < | + | * start POPFile, |
- | * go to the Advanced Tab in the < | + | * go to the Advanced Tab in the POPFile UI, |
* search for the variable IMAP_enabled in the right table and set it to 1. | * search for the variable IMAP_enabled in the right table and set it to 1. | ||
* Click the " | * Click the " | ||
- | * shut-down | + | * shut-down POPFile, |
* and start it again. | * and start it again. | ||
- | IMAP.pm should now be running along with < | + | IMAP.pm should now be running along with POPFile. |
You do not have to make any changes to your mail client configuration to work with POPFile' | You do not have to make any changes to your mail client configuration to work with POPFile' | ||
+ | |||
===== Configuring IMAP.pm ===== | ===== Configuring IMAP.pm ===== | ||
- | To configure the module, go to the Configuration tab in the < | ||
- | First, enter the connection details for your IMAP server, i.e. the server' | + | To configure the module, go to the Configuration tab in the POPFile UI. Before you do that, however, you might want to use your mail client to create folders on your IMAP server that will receive the classified messages. For example, you might want to create a folder named " |
+ | |||
+ | First, enter the connection details for your IMAP server, i.e. the server' | ||
In the next configuration step, you need to tell the module about the IMAP folder that receives incoming messages (usually the INBOX folder), and the output folders where the classified messages should go. You need to use your mail client to create new folders on the server that correspond to your buckets. Click the " | In the next configuration step, you need to tell the module about the IMAP folder that receives incoming messages (usually the INBOX folder), and the output folders where the classified messages should go. You need to use your mail client to create new folders on the server that correspond to your buckets. Click the " | ||
Line 55: | Line 55: | ||
! Check this box if you want IMAP.pm to issue an EXPUNGE command to the IMAP server after it has moved messages out of a folder. Beware -- this will also EXPUNGE messages that you have marked for deletion within your client. | ! Check this box if you want IMAP.pm to issue an EXPUNGE command to the IMAP server after it has moved messages out of a folder. Beware -- this will also EXPUNGE messages that you have marked for deletion within your client. | ||
? Update interval | ? Update interval | ||
- | ! Enter the number of seconds between status updates. How often should IMAP.pm check your mailbox? | + | ! Enter the number of seconds between status updates. How often should IMAP.pm check your mailbox? |
? Bytes to use per message | ? Bytes to use per message | ||
! The number of bytes/ | ! The number of bytes/ | ||
? Debug level | ? Debug level | ||
- | ! In the latest versions on cvs there is no longer an IMAP specific debug level. | + | ! POPFile has a global debug level that can be changed via the Advanced Tab -- change the variable " |
Clicking on " | Clicking on " | ||
===== Reporting bugs ===== | ===== Reporting bugs ===== | ||
+ | |||
If you find any bugs (or have any questions), go to the [[http:// | If you find any bugs (or have any questions), go to the [[http:// | ||
===== Links ===== | ===== Links ===== | ||
+ | |||
We have started a [[ExperimentalModules: | We have started a [[ExperimentalModules: | ||
If you would like to know about the proposed future of the POPFile IMAP module, checkout the [[ExperimentalModules: | If you would like to know about the proposed future of the POPFile IMAP module, checkout the [[ExperimentalModules: | ||
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.