MBOX-Line: From bill.shannon at sun.com  Wed Apr 11 16:44:04 2007
To: imap-protocol@u.washington.edu
From: Bill Shannon <bill.shannon@sun.com>
Date: Fri Jun  8 12:34:39 2018
Subject: [Imap-protocol] AppleMail contact?
In-Reply-To: <695752686.196811176330674108.JavaMail.root@dogfood.liquidsys.com>
References: <695752686.196811176330674108.JavaMail.root@dogfood.liquidsys.com>
Message-ID: <461D72C4.2060507@sun.com>

Dan Karp wrote:
>> Does anyone here have any contacts in the AppleMail organization? I'm
>> getting more and more complaints about JavaMail being unable to parse
>> messages that turn out to be incorrectly formatted messages created by
>> AppleMail.  I'd like to find someone to fix the problem at the source
>> rather than continue to add workarounds for their bugs.
> 
> Other than RFC 2231 issues (and we're happy to provide a 2231-capable header
> parser in Java if you want one), what brokenness have you been seeing from
> AppleMail?

A Content-Disposition header of this form:

Content-Disposition: filename="Scan1852.pdf";
	filename="Scan1852.pdf"

(Again, claimed by a user of JavaMail, not seen by me personally.)

See the end of this discussion thread:
http://forum.java.sun.com/thread.jspa?forumID=43&threadID=5145629

JavaMail parses most RFC 2231 headers, and I'll update it to handle the
missing cases, but the problems there have been that AppleMail doesn't
quote parameter values when it should.  I have hacks to handle the simplest
case of that error.

Do you have a contact in the AppleMail group?

