Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 137 of 808  Not logged in ELOG logo
    icon2.gif   Re: XML password files, replication & FreeBSD, posted by Stefan Ritt on Wed Apr 13 09:06:46 2005 
> Ok, i see, the problem for me now is that this attribute name has been in use for 
> half a year or so by me. So now I have 100's of logbook entries with the old name 
> in them, if I change it's name then all old logbook entries will show up with that 
    icon2.gif   Re: Conditional conditions?, posted by Stefan Ritt on Wed Apr 13 10:06:56 2005 
> Can conditional attributes be assigned as conditions?

Well, I guess the question was: "Can you implement this?" I'm sure that you
    icon2.gif   Re: MIME encoding of mail?, posted by Stefan Ritt on Thu Apr 14 15:42:44 2005 
> What I can see is that it sends with charset=US-ASCII, even if the characters are
> non-US.
    icon2.gif   Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 15:25:30 2005 
So you tell me that the message body is ok with Norwegian characters, it's only the subject?
That would mean that outlook interpretes the charset only for the message body, but not for
the subject. So if you have characters with an ASCII value greater than 127, your mail
    icon2.gif   Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 15:57:53 2005 
Ok, I found it. It's in RFC2047 at

http://www.faqs.org/rfcs/rfc2047.html
    icon2.gif   Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 21:10:27 2005 
I implemented this, but found some problems. If I encode the subject like

Subject: =?ISO-8859-1?Q?ורז?=
    icon2.gif   Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 21:14:05 2005 
> Subject: Testing ורז

> Becomes
    icon2.gif   Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 21:49:00 2005 
> If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> Maybe that could be a solution?
ELOG V3.1.5-3fb85fa6