Custom Query (332 matches)


Show under each result:

Results (52 - 54 of 332)

Ticket Resolution Summary Owner Reporter
#175 fixed TD: saving email to /tmp/xxx error when trying to email to blog bas roland.wells@…

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:

saving email to /tmp/tmpr3914I.email2trac

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

#18 fixed Support replying to ticket notifications bas chrivers@…

I'm trying to use trac+email2trac as a request tracket for the support@ email address at our company.

It mostly works, except for the following problems:

1) If the reporter answers to a notification email, that email is either sent from support@company, in which case the reply becomes a _new_ ticket, or it's sent from <other>@company, in which case it's not tracked. It doesn't seem to be possible to track replies to notifications, as replies in trac.

2) It's not possible to exclusively use trac, since for example you cannot attach files when replying to tickets. I don't want to use trac exclusively either, since my mail client is much nicer to compose mails in.

To solve these problems, I suggest something like the following scenario:

  • The ticket number is put in the subject, like with RequestTracker? ("Ticket #42: Question about foo")

  • A customer, bob@… has a request for support@…. He sends his question like a normal email (which pipes into email2trac)
  • The company recieves a new ticket notification from trac (or email2trac), with the Reply-to header set to support@…. They reply to bobs request.
  • Email2trac now gets another notification. This time it contains a valid ticket number in the subject, so email2trac can know it's a reply to a ticket, not a new ticket. The new text gets added as a reply to the ticket, and bob@… is sent the new reply as well.
  • Bob has further questions, so he replies back to the ticket notification
  • Bobs reply is again added as a reply in trac, and the company receives his reply
  • The company this time send the final information to bob, and adds "FIXED" in the subject.
  • The reply from the company is added in trac, and the ticket is closed. The reply is sent to bob.

I hope you can see the idea I have for using trac as a sort of mediator, or ticket gateway, if you will. As far as I can see, it should already be able to update tickets, although I have not successfully made this work yet.

Can you tell me what kind of work would be required to make email2trac act as outlined here? Would patches be accepted?

#413 fixed Support for Trac version 1.2 bas sbroadhead@…

Recently upgraded our Trac system to version 1.2 and broke our email2trac functionality. Am seeing the following in our syslog:

"Mar 13 14:44:08 <tracserver> email2trac <trac_proj>: TRAC version 1.2 is not supported"

<tracserver> and <trac_proj> replacements for specific values.

Will Trac 1.2 be supported soon?

Also... upgraded to email2trac version 2.10

Note: See TracQuery for help on using queries.