Changes between Version 8 and Version 9 of MailToTracPlugin
- Timestamp:
- Oct 27, 2011, 11:47:29 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MailToTracPlugin
v8 v9 20 20 }}} 21 21 22 === Processing mail from a third-party mailserver === 23 If 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 25 Example fetchmail command: 26 27 {{{ 28 fetchmail --protocol POP3 --port 110 --user [mailaccount] --mda "mail2trac -p /path/to/trac/environment" mailhost.domain.com 29 }}} 30 22 31 == Why not email2trac? == 23 32 … … 31 40 32 41 While 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.com41 }}}42 42 43 43 == Bugs/Feature Requests ==