| 22 | == Why not email2trac? == |
| 23 | |
| 24 | EmailToTracScript 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 | |
| 26 | MailToTracPlugin 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 | |
| 32 | 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. |