Custom Query (332 matches)

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?

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,

Thanks for this great project, it is very useful for us.

I have various Trac projects working well on the same box and I would like to use a different email address per project. up until now we have only need to use email2trac in one project, is it possible to use for another one?

As I said before /etc/email2trac.conf is setup and happily working for the "trac-systems" and I would like to add "trac-sdlc" (the last 5 lines) but no luck.

These are the config files

Thank you.

[DEFAULT]
project: /home/trac/trac-environments/trac-systems/
debug: 0
umask: 011
spam_level: 0
reply_all : 1
mailto_link: 0
ticket_update : 1
email_header: 0
trac_version: 0.11
enable_syslog : 1
alternate_notify_template :
alternate_notify_template_update :
drop_spam : 0
verbatim_format: 1
strip_signature: 1
email_quote: >
strip_quotes: 0
ignore_trac_user_settings: 0
black_list: MAILER-DAEMON@
binhex: warn
applesingle: warn
appledouble: warn


[trac-systems]
default_componenet : Desktop
default_priority : 5 - Lowest
default_type : Issue
default_version : 0.70

[trac-sdlc]
default_componenet : Unknown
default_priority : major
default_type : defect
default_version : 0.70

$ cat /home/sdlcmail2trac/.fetchmailrc
server mail.example.org
  proto IMAP
  user sdlc-trac
  pass passwd
  mda "/usr/bin/email2trac"

# cat trac-sdlc/conf/trac.ini
...
[notification]
smtp_always = true
smtp_from = sdlc-trac@example.org
smtp_replyto = sdlc-trac@example.org
smtp_server = localhost
ticket_subject_template = Auto Generated Ticket #$ticket.id: $summary
...

$ /usr/bin/fetchmail -v 
fetchmail: 6.3.6 querying mailserver.us.org (protocol IMAP) at Tue 22 Sep 2009 12:59:55 PM BST: poll started
Trying to connect to 192.9.200.18/143...connected.
fetchmail: IMAP< * OK (Linux/i686) IMAP4rev1 service is ready
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 CHILDREN IDLE LITERAL+ MULTIAPPEND NAMESPACE UIDPLUS QUOTA STARTTLS AUTH=CRAM-MD5 AUTH=LOGIN AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=GSSAPI ACL RIGHTS=texkbn
fetchmail: IMAP< A0001 OK Done CAPABILITY
fetchmail: IMAP> A0002 STARTTLS
fetchmail: IMAP< A0002 OK Done STARTTLS
fetchmail: Issuer Organization: 
fetchmail: Issuer CommonName: mail.example.org
fetchmail: Server CommonName: mail.example.org
fetchmail: mail.example.org key fingerprint: F7:3E:B1:27:57:05:E1:D5:93:7A:DB:51:CD:0F:73:57
fetchmail: Server certificate verification error: self signed certificate
fetchmail: IMAP> A0003 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 CHILDREN IDLE LITERAL+ MULTIAPPEND NAMESPACE UIDPLUS QUOTA AUTH=CRAM-MD5 AUTH=LOGIN AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=GSSAPI ACL RIGHTS=texkbn
fetchmail: IMAP< A0003 OK Done CAPABILITY
fetchmail: mail.example.org: upgrade to TLS succeeded.
fetchmail: IMAP> A0004 AUTHENTICATE GSSAPI
fetchmail: IMAP< A0004 NO Failed AUTHENTICATE
fetchmail: Sending credentials
fetchmail: Error exchanging credentials
fetchmail: IMAP< * BAD Error: Parsing string
fetchmail: IMAP> A0005 *
fetchmail: IMAP> A0006 AUTHENTICATE CRAM-MD5
fetchmail: IMAP< A0005 BAD Error: Unexpected item 
fetchmail: could not decode BASE64 challenge
fetchmail: IMAP> A0007 *
fetchmail: IMAP> A0008 LOGIN "sdlc-trac" *
fetchmail: IMAP< + PDMzNjM4NTIzMDEuMTIxMDY4ODZAbWFpbC5tYWdsYWJzLm5ldD4=
fetchmail: IMAP< A0006 BAD Error: Expected char CR not found
fetchmail: IMAP< A0008 OK Done LOGIN
fetchmail: IMAP> A0009 SELECT "INBOX"
fetchmail: IMAP< * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
fetchmail: IMAP< * 1 EXISTS
fetchmail: IMAP< * 0 RECENT
fetchmail: IMAP< * OK [UNSEEN 1] First unseen message
fetchmail: IMAP< * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
fetchmail: IMAP< * OK [UIDNEXT 2] Predicted next UID
fetchmail: IMAP< * OK [UIDVALIDITY 1530465953] UIDs valid
fetchmail: IMAP< A0009 OK [READ-WRITE] Done SELECT
fetchmail: IMAP> A0010 EXPUNGE
fetchmail: IMAP< A0010 OK Done EXPUNGE
fetchmail: IMAP> A0011 SEARCH UNSEEN NOT DELETED
fetchmail: IMAP< * SEARCH 1
fetchmail: IMAP< A0011 OK Done SEARCH
1 message for sdlc-trac at mail.example.org.
fetchmail: IMAP> A0012 FETCH 1 RFC822.SIZE
fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 557)
fetchmail: IMAP< A0012 OK Done FETCH
fetchmail: IMAP> A0013 FETCH 1 RFC822.HEADER
fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {551}
reading message sdlc-trac@mail.example.org:1 of 1 (551 header octets)
#
fetchmail: IMAP< )
fetchmail: IMAP< A0013 OK Done FETCH
fetchmail: IMAP> A0014 FETCH 1 BODY.PEEK[TEXT]
fetchmail: IMAP< * 1 FETCH (BODY[TEXT] {6}
 (6 body octets)*
fetchmail: IMAP< )
fetchmail: IMAP< A0014 OK Done FETCH
fetchmail: MDA returned nonzero status 1
 not flushed
fetchmail: IMAP> A0015 LOGOUT
fetchmail: IMAP< * BYE AXIGEN IMAP4rev1 service is logging out
fetchmail: IMAP< A0015 OK Done LOGOUT
fetchmail: 6.3.6 querying mail.example.org (protocol IMAP) at Tue 22 Sep 2009 12:59:56 PM BST: poll completed
fetchmail: normal termination, status 0