Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Email subject garbaged when set?, posted by Chris Green on Wed Jul 27 17:30:38 2005 
    icon2.gif   Re: Email subject garbaged when set?, posted by Stefan Ritt on Thu Aug 4 22:59:12 2005 
       icon2.gif   Re: Email subject garbaged when set?, posted by Chris Green on Fri Aug 5 01:13:13 2005 
       icon2.gif   Re: Email subject garbaged when set?, posted by Heiko Scheit on Fri Aug 5 11:18:08 2005 
          icon2.gif   Re: Email subject garbaged when set?, posted by Stefan Ritt on Fri Aug 5 12:37:42 2005 
Message ID: 1375     Entry time: Thu Aug 4 22:59:12 2005     In reply to: 1350     Reply to this: 1376   1384
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Linux  ELOG Version: 2.6.0b3 
Subject: Re: Email subject garbaged when set? 

Chris Green wrote:
The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.


This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject?
ELOG V3.1.5-fe60aaf