Custom Query (332 matches)


Show under each result:

Results (256 - 258 of 332)

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

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

#271 fixed Fix for problem with filenames on native language (Russian) bas slevin@…

Strange situation, #247 "to be continied" In attachments log-file of email2trac v.2.4.0(from svn). We're get offten errors on our trac in production mode. Files with short names on russian are stay problem for email2trac.

#272 fixed how does email2trac parses the to-field bas anonymous

I set om@… as my recipient_list.And we have another email aom@…. When i send an email to aom@… from om@…, a ticket is created. is it because of the aom/om? or just a matter of misconfiguration.

Note: See TracQuery for help on using queries.