Modify

Opened 11 years ago

Closed 11 years ago

#167 closed setup (invalid)

attachments cause an infinite loop

Reported by: ubuntu@… Owned by: bas
Priority: critical Milestone:
Component: email2trac Version: 1.0.0
Keywords: Cc:

Description

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...

Attachments (0)

Change History (2)

comment:1 Changed 11 years ago by bas

  • Status changed from new to assigned
  • Type changed from defect to setup

Just back from holidays. I have not seen this problem, but i do not use fetchmail. Is there something in the syslog file or another log file. Maybe email2trac retuns an error and fetchmail will try it over and over again.

comment:2 Changed 11 years ago by ubuntu@…

  • Resolution set to invalid
  • Status changed from assigned to closed

You guessed it. I was futzing with email2trac and broke it. The non-zero return code would cause fetchmail to NOT delete the message from the IMAP server. On the next fetchmail poll, the message would be fetched -- again -- and would grab the attachment -- again.

From the fetchmail man page: "It means that if a message is fetched (and thus marked seen by the mailserver) but not delivered locally due to some transient error, it will be re-fetched during the next poll cycle."

I used the SQLite Database Browser to run some SQL queries to clean out my ~600 duplicate tickets.

Add Comment

Modify Ticket

Change Properties
Action
as closed The owner will remain bas.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.