Changes between Version 3 and Version 4 of MailToTracPlugin


Ignore:
Timestamp:
Oct 11, 2009, 6:00:00 PM (5 years ago)
Author:
k0s
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MailToTracPlugin

    v3 v4  
    2020}}}
    2121
     22== Why not email2trac? ==
     23
     24EmailToTracScript is a more mature solution for converting email to Trac tickets.  When building the GeoTicketPlugin, I was originally  hoping to make use of the EmailToTracScript to allow emails to specify a location in the subject header (see: source:geoticketplugin/0.11/geoticket/mail.py).  When I realized the architecture would not easily support this, I thought of forking it, then realized that an implementation from scratch would actually better serve my needs.
     25
     26MailToTracPlugin offers:
     27
     28 * a real pluggable architecture that allows arbitrary email handlers to be plugged in
     29 * POSTing to a URL to avoid complicated setuid issues with MTAs
     30 * outside of configuring postfix and MX records (always fun!) an easy installation
     31
     32While 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.
    2233
    2334== Bugs/Feature Requests ==