Custom Query (332 matches)

This is related to ticket #126.

I'm using v 1.0.0 of email2trac and v 0.11 of Trac, and found that the egg cache problem has not been wholly fixed. I had to make the following change after the call to ReadConfig?(), but before the call to Environment(). Without this change, I got a traceback that it was trying to use a .python-eggs directory under the sendmail directory tree (/var/spool/mqueue/.python-eggs) when Environment() is called.

if settings.has_key('python_egg_cache'):

python_egg_cache = str(settingspython_egg_cache?) os.environPYTHON_EGG_CACHE? = python_egg_cache

Dennis

when we send an email to the email2trac address we get the following python error.

i've looked through the archives and couldn't find anything similar (surprisingly)

help! :)

<support@…>: Command died with status 1:

"PYTHON_EGG_CACHE=/var/trac; export PYTHON_EGG_CACHE; /usr/local/bin/email2trac --ticket_prefix=vsc_trac". Command output: TD: saving email to /tmp/tmpGxSGuz.email2trac

Reporting-MTA: dns; methodics-da.com X-Postfix-Queue-ID: 64A8E20B9C X-Postfix-Sender: rfc822; simon@… Arrival-Date: Sat, 20 Feb 2010 19:45:02 -0800 (PST)

Final-Recipient: rfc822; support@… Original-Recipient: rfc822;support@… Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; TD: saving email to /tmp/tmpGxSGuz.email2trac

From a customer support perspective can ticket items be collaborated on internally (as they are currently with Trac) and then only at the end a reply specified to the original sender?

If not please consider this a feature request.

Thanks!