Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (316 - 318 of 332)

Ticket Resolution Summary Owner Reporter
#141 duplicate Attachment with "ü" causes python error an is not attached bas hju@…
Description

We found a problem with python-code execution if there is an german "Umlaut" (ü) in the filename of an attachment.

email2trac produces an error in the user.log of the server { Mar 10 17:00:04 ks35958 email2trac: Traceback (most recent call last): Mar 10 17:00:04 ks35958 email2trac: File "/usr/bin/email2trac", line 1249, in ? tktparser.parse(sys.stdin) Mar 10 17:00:04 ks35958 email2trac: File "/usr/bin/email2trac", line 818, in parse self.new_ticket(m, spam_msg) Mar 10 17:00:04 ks35958 email2trac: File "/usr/bin/email2trac", line 757, in new_ticket str = self.attachments(msg, tkt) Mar 10 17:00:04 ks35958 email2trac: File "/usr/bin/email2trac", line 1049, in attachments url_filename = urllib.quote(filename) Mar 10 17:00:04 ks35958 email2trac: File "urllib.py", line 1110, in quote res = map(safe_map.getitem, s) Mar 10 17:00:04 ks35958 email2trac: KeyError?: u'\xfc' }

The ticket is created, but the attachment is not added.

Tracking down the error leads to an python-error in 2.4. The routine "quote", trying to encode special characters in the filename as "%<##>", returns an KeyError? with "\xfc" (ü).

http://bugs.python.org/issue3300

However: Is there possible workaround usin another python-function?

We use a trunk-version (218) of Version 0.30

P.S.: in another environment, we are using email2trac version 0.80 with python 2.5 under windows... Under this circumstances, there is no ticket createt at all...

#270 fixed Attachments of type "Text/Plain" are not attached if more than one attachment is sent bas hju@…
Description

I'm facing a strange effect with attachments.

We use blat 2.6.2 to send logfiles from batchjobs using the "-attach" parameter. If there is only one file "file1.txt", this file of type "TEXT/PLAIN" is attached and processed fine with email2trac (means: attached to a new ticket)

I've extended the processing to send three attachments:

  • file1.txt
  • file2.txt
  • file3.dimport

All files are simple text-files

In this case, file3 is of type "APPLICATION/OCTET-STREAM" (depends on extension, i guess). Only file3.dimport is attached. The other files are ignored (no warning or error).

I changed the blat parameter to "-attacht" to attach the logs as Text-Attachments. The mail-attachments are now all of type "TEXT/PLAIN", but nothing is attached by email2trac (no warning or error)

Looking at the code, it themes clear because this attachments are explicitly excluded in def get_message_parts(self, msg):

    def get_message_parts(self, msg):
    ...
        for part in msg.walk():
            ...
            ## Save all non plain text message as attachment
            #
            if not content_type in ['text/plain']:

Strange that a single TEXT/PLAIN attachment is processed by email2trac...

Maybe it's a solution to remove this restriction, but I think this is not restricted without reason. In older versions of email2trac, this part was handled different...

#167 invalid attachments cause an infinite loop bas ubuntu@…
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...

Note: See TracQuery for help on using queries.