Changes between Version 7 and Version 8 of MailArchivePlugin


Ignore:
Timestamp:
Dec 18, 2016, 4:02:32 PM (7 years ago)
Author:
figaro
Comment:

Moved example to functional description

Legend:

Unmodified
Added
Removed
Modified
  • MailArchivePlugin

    v7 v8  
    55== Description
    66
    7 This plugin adds a new main menu item '''Mail Archive''' that can be used to browse and view archived emails and email attachments.
     7This plugin allows you to browse and view archived emails and email attachments. It adds a new item '''Mail Archive''' to the main menu.
    88
    99Key features:
    10 * Import emails to Trac's database from an IMAP account
    11 * A new `mailarchive` resource realm
    12 * `mailarchive:` wiki links (plus `mail:`, `email:`, and `emailarchive:` synonyms)
    13 * `[[MailQuery(searchterm)]]` macro
    14 * New `trac-admin mailarchive fetch` command
    15 * New Trac permission `MAIL_ARCHIVE_VIEW`
    16 * Trac Search integration
     10* Import emails to Trac's database from an IMAP account.
     11* A new `mailarchive` resource realm.
     12* `mailarchive:` wiki links, plus `mail:`, `email:`, and `emailarchive:` synonyms.
     13* The macro `[[MailQuery(searchterm)]]` in your wiki page allows you to search archived mails.
     14* New `trac-admin mailarchive fetch` command.
     15* New Trac permission `MAIL_ARCHIVE_VIEW`.
     16* Trac Search integration.
     17
     18For example, you can schedule a task to call the following command every 15 minutes:
     19{{{#!sh
     20$ trac-admin path/to/trac/environment mailarchive fetch imap.example.com trac-archive@example.com password123
     21}}}
     22
     23Make sure that the emails to be archived are marked as unread or very recent, ie from today, as only such emails will be considered for archiving.
    1724
    1825=== Known Problems
    1926
    20 * A reset of uids on the IMAP server could lead to problems, eg duplicate / unarchived emails (#11535)
     27* A reset of uids on the IMAP server could lead to problems, eg duplicate / unarchived emails (#11535).
    2128
    2229== !Bugs/Feature Requests
     
    4855}}}
    4956
    50 A database upgrade will be required as usual: `trac-admin path/to/trac/environment upgrade`.
     57A database upgrade will be required as usual:
     58{{{#!sh
     59$ trac-admin path/to/trac/environment upgrade
     60}}}
     61
     62== Configuration
    5163
    5264Assign the new `MAIL_ARCHIVE_VIEW` permission to the appropriate Trac groups / users, eg in Trac's permission admin page.
     
    5466Additionally you need an email IMAP account that only contains all the emails you want to archive. If you don't already have this, you could create a new separate email account (e.g. `trac-archive@example.com`) and copy all emails you want to appear in Trac's mail archive to that account.
    5567
    56 Actually archiving the emails from that IMAP account into Trac's database must be done separately using a new `trac-admin mailarchive fetch <host> <username> <password>` command. You should configure (e.g. using a cron job in Unix, or using a scheduled task in Windows) it to be periodically called. Replace `<host>`, `<username>` and `<password>` with your email host, username and password.
    57 
    58 == Example
    59 
    60 Schedule a task to call the following command every 15 minutes: `trac-admin path/to/trac/environment mailarchive fetch imap.example.com trac-archive@example.com password123`
    61 
    62 Make sure that the emails to be archived are marked as unread or very recent, ie from today, as only such emails will be considered for archiving.
     68Actually archiving the emails from that IMAP account into Trac's database must be done separately using a new `trac-admin mailarchive fetch <host> <username> <password>` command. You should configure it to be periodically called, for example by using a cron job in Unix or using a scheduled task in Windows. Replace `<host>`, `<username>` and `<password>` with your email host, username and password.
    6369
    6470== Recent Changes