Guillermo Grandes (JIRA) wrote:
[ http://issues.apache.org/jira/browse/JAMES-648?page=comments#action_12439680 ] Guillermo Grandes commented on JAMES-648:
-----------------------------------------

Anyway... My big problem is not the "ó" corrupted in an "ó", my problem is the corrupted 
Mime Boundary "------_=_NextPart_000_01C0B2DF.DE9D0F20"

IMHO... this is not... "normal"

if I add the missing header "Content-Transfer-Encoding: 7bit" or "8bit", the 
mime-boundaries are OK and message is not corrupt, this is my question, why JavaMail use 
"quoted-printable" for missing header instead of Xbit?
IMO, if a char >127 is found in the stream and no header is set, we have 2 
options:
1) recode the chars with =HH and set quoted-printable
2) set header to 8bit

this is the correct, right?


I think that you wrote 20 messages in this JIRA issue and I still don't understand what exactly happens.

In this message you talk about an "ó" corrupted in an "ó": I had not seen this explanation in any previous log/attachment/comment. Can you write a single message where you write the SMTP conversation in input, any middle passage you can trace/log and the result?

I would like to understand if my idea that your client is talking to JAMES like it exposed the 8BITMIME extension is right or not and if having an 8bitmime support would be or not the solution to your issue.

As an example I don't know if "your" (non-rfc-compliant) client is using HELO or EHLO as the salutation in the SMTP conversation.

And please use the mailing list for this and not JIRA: we have not threads in JIRA and it will be a mess if we have 100 unthreaded messages there. As soon as the scenario will be more clear you (or we) can add the result of the discussion to the issue.

Stefano

PS: I will be against applying any code change or patch based on assumptions and not on a clear analysis of what happened when we talk about relaxed interpretation of the rfc.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to