Custom Query (332 matches)

run_email2trac will not run at all on my system. In my maillog I see:

postfix/local[14530]: 4CBD454659: to=<trac@hidden.....com>, relay=local, delay=0.14, delays=0.05/0.06/0/0.04, dsn=5.3.0, status=bounced (Command died with status 254: "/usr/local/bin/run_email2trac")

What does this mean and how do I fix it?

I replied to a trac ticket email, and it didn't work. The command aborted with error 1 so I got a mailer-daemon reply for that. In syslog I see:

Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment: subject: u'Re: [thismoment] #15002: Make email2trac work'
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment: Traceback (most recent call last):
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment:   File "/usr/local/bin/email2trac", line 2571, in ?     tktparser.parse(sys.stdin)
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment:   File "/usr/local/bin/email2trac", line 1714, in parse     if not self.ticket_update(m, result.group('reply')[:-1], spam_msg):
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment:   File "/usr/local/bin/email2trac", line 1010, in ticket_update     tkt.save_changes(self.author, body_text, when, None, str(cnum))
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment:   File "build/bdist.linux-i686/egg/trac/ticket/model.py", line 289, in save_changes
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment:   File "build/bdist.linux-i686/egg/trac/db/api.py", line 78, in transaction_wrapper
Dec 22 10:32:47 ip-10-166-254-128 email2trac thismoment: OperationalError: database or disk is full

My disk is not full, and adding comments through the web interface works normally, so I assume the database isn't full either.

# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1            103212320  48780892  49189700  50% /
/dev/sdf              51593181   8160798  40810943  17% /var/svnbak
none                    890952         0    890952   0% /dev/shm

Hi,

after a long time of inactivity on the Debian package for
email2trac, I'm planning now an upload of the current version
2.4.5. There are two bugs open, which I have patched on my
production server, but I was never confident, that my patches
are correct, nor do I know whether they are necessary for the
current version. Could you maybe take a look at them?

 1. Error on wrongly encoded e-mail
    http://bugs.debian.org/593613
 2. Support for X-Spam-Flag/-Result
    http://bugs.debian.org/644916

Thanks in advance!

Cheers