Custom Query (332 matches)


Show under each result:

Results (13 - 15 of 332)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#167 invalid attachments cause an infinite loop bas ubuntu@…

Hi, I've been using email2trac and I absolutely love it. Thanks!

However, I've discovered a critical bug. When a user submits an attachment, email2trac gets stuck in some kind of infinite loop, and it reprocesses the email (and the attachment) dozens (or even hundreds?) of times. The attachment gets added to the ticket many, many times, and I'm forced to just delete the ticket to clear up the mess.

Has anyone else seen this?

I'm a Python developer and I'm happy to troubleshoot this problem (and submit a fix), but I need to know where to look.

email2trac gets its emails (and attachments) from fetchmail. So I guess it could be fetchmail causing the problem...(?)

If anyone else sees this please post here, so I know whether or not it's just my particular configuration...

#8 invalid With restrict_owner=true ticket is not created. bas TYatsurak@…

Trac 0.10.4 using apache, email2trac 0.9.5

restrict_owner=true in trac.ini, component Support has valid owner, get_known_users query shows all users with fully specified names.


cat msg.txt|email2trac --component=Support Traceback (most recent call last):

File "/usr/local/bin/email2trac", line 974, in ?


File "/usr/local/bin/email2trac", line 560, in parse


File "/usr/local/bin/email2trac", line 432, in new_ticket

tkt = Ticket(self.env)

File "/usr/lib/python2.4/site-packages/trac/ticket/", line 37, in init

self.fields = TicketSystem?(self.env).get_ticket_fields()

File "/usr/lib/python2.4/site-packages/trac/ticket/", line 104, in get_ticket_fields

for username, name, email in self.env.get_known_users(db):

File "/usr/lib/python2.4/site-packages/trac/", line 320, in get_known_users

for username,name,email in cursor:

File "/usr/lib/python2.4/site-packages/trac/db/", line 40, in iter

row = self.cursor.fetchone()

File "/usr/lib/python2.4/site-packages/pyPgSQL/", line 3158, in fetchone

raise Error, \

Error: fetchone() failed - cursor does not contain a result. TD: saving email to /tmp/tmpT0AepR.email2trac ---

#354 fixed qmail configuration example bas ttt@…

I would like to contribute with a full working example of qmail setup
for a multi Trac environment, making use of the parentdir configuration
option of email2trac.

You can add it all or in parts to the instructions page if you like.

Note that I could get the --virtualenv option to work for me and I had
to explicitly run the script with the Python from the desired
VirtualEnv. Maybe there is some bug in the VirtualEnv setting in
email2trac or wrong usage by me, I did not have enough time to find the
root cause and I could work around the problem.

Thank you for your effort developing and supporting this valuable
integration point between email system and Trac.

Best regards.

= qmail Configuration

This configuration was based on the following references:
 * man qmail-users

Configuration changes:

 * To accept emails for the new domain:
root@server:/etc/qmail# echo >> rcpthosts

 * To declare the new domain as a virtual domain, to ensure namespace
separation of local usernames:
root@server:/etc/qmail# echo >>

 * Add a rule to match all possible users of the new virtual domain to a
directory where per-user .qmail files determine further processing of
messages, running as www-data user:
root@server:/etc/qmail# sed -i

 * Make changes take effect:
root@server:/etc/qmail# qmail-newu
root@server:/etc/qmail# /etc/init.d/qmail restart

 * Put per-user .qmail files in place, making messages go to the
email2trac script:
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=one' > .qmail-one
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=two' > .qmail-two
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=three' > .qmail-three
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.