Custom Query (332 matches)

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

Hello,

We're using a Trac instance for both internal and customer-facing ticket reports, and want to be able to reply to tickets to send a customer (the reporter on an auto-generated ticket). However, we don't want to use the always_notify_reporter option in Trac, to avoid mailing developers about normal tickets.

Thus, we need a way to mail a reporter about Email2Trac tickets only. I believe the easiest way to do this would be to set a cc field on ticket creation with the email of the reporter. However, to my knowledge a default_cc field in email2trac.conf would not accept a reporter variable.

Could there be an option to automatically add the reporter (which, with email2trac, will always be an email address) to the CC field of any new tickets?

At our installation we are using email_default_domain (or smtp_default_domain) for all users; that way no one has to set their email_address on their preferences, but when they open a ticket using email2trac the system believes that they are not valid users.

I'm attaching a patch to enable the use of a email_default_domain on the email2trac configuration to avoid that case; with the patch if someone with an address of the form USER@DEFAULT_DOMAIN sends a message and there is an entry for USER on the session table then the ticket is created by USER.

Note that the patch does not apply cleanly to the current trunk because of the changeset:481, but the fix is trivial... ;)