Edgewall Software
Modify ↓

Opened 14 years ago

Closed 14 years ago

#10216 closed defect (invalid)

messages in base64 unreadable - roundcube 0.5.3

Reported by: dinosaurusss@… Owned by:
Priority: normal Milestone:
Component: general Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

hello,

I encounter a problem that I had not before.

Roundcube fails to decode some parts of messages encoded in base64.

Looking more closely at the posts concerned, I realize that roundcube encounter this problem when the body of the post is long and the source contains several strings in base64 (each string with 2068 caracters) and with a space before the strings.

through a mail client, the message is decoded normaly. with roundcube, the message is partially decode.

infos system : ubuntu server 10.04.2 LTS php 5.3.2 mysql 5.1.41

Attachments (1)

body2.txt​ (9.7 KB ) - added by anonymous 14 years ago.

Download all attachments as: .zip

Change History (2)

by anonymous, 14 years ago

Attachment: body2.txt​ added

comment:1 by Christian Boos, 14 years ago

Resolution: → invalid
Status: new → closed

I suppose you're not talking about base64 encoded mails sent by the Trac notification system, right?

Then you're on the WrongTrac, look at ​http://trac.roundcube.net/wiki instead.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.