Changes between Version 8 and Version 9 of MailToTracPlugin


Ignore:
Timestamp:
Oct 27, 2011, 1:47:29 PM (3 years ago)
Author:
Floris
Comment:

Moved fetchmail description right under postfix

Legend:

Unmodified
Added
Removed
Modified
  • MailToTracPlugin

    v8 v9  
    2020}}}
    2121
     22=== Processing mail from a third-party mailserver ===
     23If your Trac server lacks postfix and you want mail2trac to handle e-mail from a distinct server, you could use [http://fetchmail.berlios.de/ Fetchmail] to download the e-mails and process them with mail2trac.
     24
     25Example fetchmail command:
     26
     27{{{
     28fetchmail --protocol POP3 --port 110 --user [mailaccount] --mda "mail2trac -p /path/to/trac/environment" mailhost.domain.com
     29}}}
     30
    2231== Why not email2trac? ==
    2332
     
    3140
    3241While mail2trac is less mature, to the front-end user there shouldn't be considerable difference for the case of creating and responding to tickets.  From a development point of view, I would recommend mail2trac over email2trac as a point to build on since a pluggable architecture was the point since the beginning.
    33 
    34 == Processing mail from a third-party mailserver ==
    35 E-mails are handled by the mail2trac executable.  Normally the mail transfer software would execute this program for each incoming mail.
    36 
    37 If your Trac installation is separate from the e-mail infrastructure, you can use use [http://fetchmail.berlios.de/ Fetchmail] to download the e-mails from the external server.
    38 
    39 {{{
    40 fetchmail --protocol POP3 --port 110 --user [mailaccount] --mda "mail2trac -p /path/to/trac/environment" mailhost.domain.com
    41 }}}
    4242
    4343== Bugs/Feature Requests ==