Custom Query (330 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 330)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#155 fixed better description for strip_signature bas tom@…
Description

I tryed to get the strip signature working - the description is not that good

you wrote: It scans the message for a line containing the string --. All lines after this line will be skipped.

but mail2trac is searching for a string that looks like this dash dash space line-return

so i think a better description in the documentation would be like this: It scans the message for a line containing the string -- . All lines after this line will be skipped. The exact String is - dash dash space line-return

-- 

kind regards
ToM

#105 fixed Better support for inline attachments and multiple body parts bas anonymous
Description

Right now, email2trac assumes that the first text part of a message is its body, and that everything else is an attachment.

With modern email clients, it's possible to create a message that has an attachment in the middle of its body. MIME represents this kind of a thing as a text/plain part followed by an image type followed by another text/plain part.

When this happens, email2trac produces a ticket whose description contains only the first part of the body, and gives it two attachments: one for the image, and one for the second part of the body. This is wrong.

The patch that I am attaching implements the following features

Proper support for multiple body parts

If a message's body is broken up into several pieces (by attachments in the middle of the message), the ticket's description is set to the entire body, not just the first part

For example, from an email like this:

some text
<some image>
more text

the ticket that is created will have "some text" and "more text" in its description

Links to attachments inside the ticket description

[attachment:filename] links are automatically placed inside the ticket description, so that message text can clearly refer to them.

For example, an email like

I opened this file in your app:
<my file>
and I got the following error dialog:
<image>

will generate a ticket like this:

I opened this file in your app:

[attachment:"my file"]

and I got the following error dialog:

[attachment:"image"]

Inline image attachments

If an attachment is of type image/* and its Content-Disposition is inline, then a Trac Image macro is placed inside the ticket description in the appropriate place, so that the resulting ticket has the image inline where it belongs in the text.

The same email as in the previous example, if the image is inline, will result in:

I opened this file in your app

[attachment:"my file"]

and I got the following error dialog:

[[Image(image)]]
#144 fixed Better Unicode support bas trumbitta@…
Description

When a non-ASCII character is in the description, the message will not be parsed and the script will exit.

I'll try to fix this figuring out where to put a .encode('utf-8') but I'm not a python programmer...

I guess this is a problem wich not only affects the description, but also other fields.

You can easily check by adding an è somewhere in the description of a ticket.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.