> Hi Holger,
> 
> > Which ELOG version do you use?
> I'am using the version V2.6.1-1653 of Elog 
> 
> > From which logbook are the screenshots? (I assume it's Liste - right?)
> Right :)!
> 
> I've just seen that Stefan has build a V2.6.1-1663 version of ELOG.
> I try to install this new version and gave you answer as soon as possible :)!

Now I'am using the Elog V2.6.1-1668 and same probleme.
I think it's a data problem. I have edited my logbooks\Liste\050302a.log with an Hexadecimal editor and found one 
carruage return juste before the 

> If an attribute uses MOptions and is also extendable, clicking "Add 
> <attribute name>" and entering a value adds the value to the MOptions, but 
> does not put the value into the log entry. The log record has that 
> attribute blank.
> You have to go back into the record and edit it to put the new value in.

I fixed that bug just now, thanks for reporting it. It's available in revision
1.535 under CVS.

> Is there anybody that use the MOptions ?
> I'am searching some example to understand this fonction could you help 
> me ? :)

You used it already! (;-)

In this forum, you clicked on OS:Windows. You can select more than one OS
(->"multi" options or MOptions). The according configuration entry is:

MOptions OS = Linux, Windows, MaxOSX, All, Other

> I would like to increase the spacing between 'MOptions' choices. I have
> created a new theme and have been playing with the CSS stylesheet. But can't
> find how to increase this spacing. Having lots of fun otherwise!

Intersting question (meaning: I don't have an answer... (;-) )

The class which applies there is "attribvalue". You can increase the padding for
that class, but that only increases the space between all options and the cell
border, but not between them. I could put each MOption in a separate cell of a
subtable. Then one could increase the padding between them, but the layout would
be fixed, meaning that they are always left-to-right. As you can see in this
forum, the MOptions nicely place below each other if the screen is too narrow.
This functionality would be lost.

Maybe someone else has a clever solution?

I just checked the current installatin, and just found one MIME-Version in the header, even with attachments:

MIME-Version: 1.0
--------------717E3059287C82F12BC14941
Content-Type: multipart/related;
  boundary="------------4543EB0E5AAC14B461D70512"

No idea where your second header comes from, but sometimes I have seen some SPAM filters adding things to headers.

Stefan

What you can try is to debug the communication between elogd and the SMTP
server. Just turn on logging via

Logfile = log.txt
Logging level = 3

After sending email, you see the conversation in log.txt. Maybe this gives you
some hints.

> What you can try is to debug the communication between elogd and the SMTP
> server. Just turn on logging via
> 
> Logfile = log.txt
> Logging level = 3
> 
> After sending email, you see the conversation in log.txt. Maybe this gives you
> some hints.


I run with loggin level = 6:
14-Apr-2005 14:50:16 [pc-0460] {ikt} Email from elog@..... to
Michael.Husbyn@.....,, SMTP host smtp......:
14-Apr-2005 14:50:16 [pc-0460] {ikt} 220 backup...... ESMTP Sendmail
8.12.11/8.12.11; Thu, 14 Apr 2005 14:59:18 +0200
14-Apr-2005 14:50:16 [pc-0460] {ikt}
14-Apr-2005 14:50:16 [pc-0460] {ikt} HELO njord......
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 backup...... Hello njord......
[10.138.224.221], pleased to meet you
14-Apr-2005 14:50:16 [pc-0460] {ikt} MAIL FROM: elog@.....
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.1.0 elog@........ Sender ok
14-Apr-2005 14:50:16 [pc-0460] {ikt} RCPT TO: <Michael.Husbyn@.....>
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.1.5 <Michael.Husbyn@.....>... Recipient ok
14-Apr-2005 14:50:16 [pc-0460] {ikt} DATA
14-Apr-2005 14:50:16 [pc-0460] {ikt} 354 Enter mail, end with "." on a line by itself
14-Apr-2005 14:50:16 [pc-0460] {ikt} To: Michael.Husbyn@.....,
14-Apr-2005 14:50:16 [pc-0460] {ikt} From: elog@.....
Subject: IKT sak (110): Testing רזו
14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Mailer: Elog, Version 2.5.8-3
14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Elog-URL: http://njord......:8090/ikt/110
14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Elog-submit-type: web|elog
14-Apr-2005 14:50:16 [pc-0460] {ikt} Date: Thu, 14 Apr 2005 14:50:16 +0200
14-Apr-2005 14:50:16 [pc-0460] {ikt} Content-Type: TEXT/PLAIN; charset=US-ASCII

14-Apr-2005 14:50:16 [pc-0460] {ikt} .
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.0.0 j3ECxI8e003851 Message accepted for
delivery
14-Apr-2005 14:50:16 [pc-0460] {ikt} QUIT
14-Apr-2005 14:50:16 [pc-0460] {ikt} 221 2.0.0 backup...... closing connection
14-Apr-2005 14:50:16 [pc-0460] {ikt} READ entry #110

--

Sorry for the late reply btw, I've removed some information in the log (server names)

What I can see is that it sends with charset=US-ASCII, even if the characters are
non-US.

Only outlooks have problem with understanding if the subject is not mime encoded.

Ideas?

Best regards
Michael Husbyn

> What I can see is that it sends with charset=US-ASCII, even if the characters are
> non-US.

That's the key point. I changed it such that elog uses now the charset defined in the
configuration file, now it should work fine. Can you give it a try? The new version is
under CVS.