Custom Query (332 matches)
Results (166 - 168 of 332)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #174 | fixed | Setting PYTHON_EGG_CACHE based on parameter for run_email2trac | bas | pepl@… |
| Description |
Since I could not get run_email2trac to run with my postfix 2.5.1/Ubuntu Hardy setup because I could not set PYTHON_EGG_CACHE in /etc/aliases (Command output: local: fatal: execvp PYTHON_EGG_CACHE=/some/path/.egg-cache: No such file or directory Works like email2trac: |"/usr/local/bin/run_email2trac --eggcache /some/path/.egg-cache" in aliases then. Patch attached |
|||
| #175 | fixed | TD: saving email to /tmp/xxx error when trying to email to blog | bas | roland.wells@… |
| Description |
email2trac works beautifully in creating new tickets and updating existing tickets, but when I try to use to post to a new (or update a) blog, I get the following error (in syslog as well as bounced to email): Command died with status 1: "/usr/local/bin/email2trac --project=olives". Command output: TD:
Final-Recipient: rfc822; trac@... Original-Recipient: rfc822;trac@... Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; TD: saving email to /tmp/tmpr3914I.email2trac FreeBSD, trac .11.6, email2trac 1.0.0, fullblog 0.1 |
|||
| #176 | worksforme | Reporter receives no more notification after update | bas | hju@… |
| Description |
After successfully updating email2trac to version 1.0.0 we face a very odd behaviour. The notification (we use alternate_notify_template - works as designed) is sent to the owner of the ticket (identified via componend) and the smtp_always_bcc adresses , but not to the reporter (who sent the mail). There was nothing changed in the configuration (always_notify_reporter=true), the reporter_states = new,closed,reopened (from FlexibleReporterNotificationPlugin) are even unchanged. If you later close the ticket, the reporter receives a mail as expected... Are there any known issues on this? |
|||
