Roundup Tracker - Issues

Issue 510597

classification
mail content-encoding not handled
Type: Severity: normal
Components: Mail interface Versions:
process
Status: closed fixed
:
: richard : grubert, richard
Priority: normal :

Created on 2002-01-30 09:19 by grubert, last changed 2002-05-02 05:13 by richard.

Messages
msg173 Author: [hidden] (grubert) Date: 2002-01-30 09:19
i will see to it if no one is quicker.

the problem is around 490 in mailgw.py
-- shortened mail

Content-Type: multipart/mixed;
        
boundary="----_=_NextPart_000_01C19F66.0A330180"

This message is in MIME format. Since your mail 
reader does not understand
this format, some or all of this message may not be 
legible.

------_=_NextPart_000_01C19F66.0A330180
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

(k=F6nnte ein Problem werden)

------_=_NextPart_000_01C19F66.0A330180
Content-Type: application/ms-tnef
Content-Transfer-Encoding: base64


msg174 Author: [hidden] (grubert) Date: 2002-02-01 07:55
Logged In: YES 
user_id=147070

fixed: encoding for first text part.

maybe one should also check on subsequet parts.

I will sleep over it.

msg175 Author: [hidden] (richard) Date: 2002-02-06 03:52
Logged In: YES 
user_id=6405

This is a more general problem of us not keeping the
encoding of the message. I've changed the summary and closed
off the duplicate issue #511633 accordingly.

msg176 Author: [hidden] (richard) Date: 2002-05-02 05:13
Logged In: YES 
user_id=6405

content encoding now handled. 
 
History
Date User Action Args
2002-01-30 09:19:17grubertcreate