Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (91 - 93 of 332)

Ticket Resolution Summary Owner Reporter
#106 fixed More versatile support for Mac attachments bas ben@…
Description

I implemented three new configuration options, having to do with treatment of attachments that include Mac-specific data.

The attached diff is relative to the changes I submitted in #105.

binhex

The BinHex encoding format is deprecated (in favor of AppleDouble MIME, see RFC 1740), but some older clients might still be using it. A file encoded with BinHex is annoying to decode unless you are on a Mac.

The binhex option can be set to one of:

  • 'keep', in which case attachments encoded with BinHex will be included in the ticket
  • 'warn', in which case attachments encoded with BinHex will be ignored, but a warning message to that effect will be included in the ticket description
  • 'drop', in which case attachments encoded with BinHex will be silently ignored

The default is 'warn'.

applesingle

Same options and meaning as for binhex option above.

appledouble

The AppleDouble encoding format is the recommended way to include Mac-specific data in a MIME message, as per RFC 1740. A file encoded with AppleDouble can easily be presented usefully on all platforms.

The applesingle option can be set to one of:

  • 'keep', in which case both the platform-neutral data and the Mac-specific data will be included in the ticket (as two separate attachments)
  • 'warn', in which case only the platform-neutral file data will be included in the ticket. Mac-specific data will be left out, but a warning message will be included in the ticket description.
  • 'strip', in which case only the platform-neutral file data will be included in the ticket. Mac-specific data will be left out with no warning.

The default is 'warn'.

#107 fixed email2trac cant format email sent by postfix bas Florian
Description

Hi

I'm trying to run email2trac with postfix. It kindof works, but just kindof.

When I test it with

mail tracproj < msg.txt

a new ticket is created, but it is not formated at all. The whole email, including headers and mime definition is part of the description of the new ticket. and there are no attachement. The body looks

From ...  Wed Mar  8 15:29:17 2006
Return-Path: <...>
X-Original-To: ...
Delivered-To: ...
Received: from surfboard.ka.sara.nl (surfboard.ka.sara.nl [145.100.6.3])
	by localhost.localdomain (Postfix) with ESMTP id 506702800682
	for <...>; Wed,  8 Mar 2006 15:29:17 +0100 (CET)
Received: from [145.100.6.134] ([145.100.6.134] RDNS failed) by
	surfboard.ka.sara.nl with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Mar 2006 15:29:17 +0100
Message-ID: <440EEA39.6070200@sara.nl>
Date: Wed, 08 Mar 2006 15:29:13 +0100
From: Bas van der Vlies <....>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: ...
Subject: Test123
Content-Type: multipart/mixed; boundary="------------070800080005060203060809"
X-OriginalArrivalTime: 08 Mar 2006 14:29:17.0140 (UTC)
	FILETIME=[AE40B940:01C642BC]

This is a multi-part message in MIME format.
--------------070800080005060203060809
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Test1234
Test1234

When I try to create a ticket with

email2trac --project=tracproj < msg.txt 

the email is created and formated just fine.

I run it with mta_user=nobody and trac_user=root (I know, it is not the best way to run it with root...)

Any idea what I missed or what I could have done wrong?

Thanks Florian

#108 fixed Apple Mail can't reply to existing tickets bas pvz@…
Description

When trying to reply to an e-mail sent by Trac, the From:-address does not appear in the To:-field. Instead it it blank. Not sure what might be causing that. Anyway, I guess that's a problem with Trac, not with email2trac, since that's what's responsible for sending out updates to start with... but since typically people don't reply to Trac tickets unless there is email2trac, I figured asking here would be a good place to start.

I'm attaching the source code of an e-mail that exhibits the described behaviour.

Note: See TracQuery for help on using queries.