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
program requires to enclose it into

=?<charset>?B?+<text>?=

Do you know that the "B" is for? I would not like to "blindly" do whatever Mutt does, I
would like to understand it. If someone can point me to a document which describes this
properly, I could implement it.

> > 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.

Tried it now, using the same charset I get when sending email from Mutt: (this is right)
Subject: Testing =?iso-8859-1?B?+Obl?=
To: michael.husbyn@.........
Message-id: <20050415125415.GA30539@njord........>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: inline
User-Agent: Mutt/1.4.1i

When sending from Elog with the same subject (from the same server):
Subject: IKT sak =?UNKNOWN?B?KDExMCk6?= Testing =?UNKNOWN?B?+Obl?=
To: Michael.Husbyn@............
Message-id: <200504151304.j3FD4aKP006491@njord..................>
MIME-version: 1.0
X-Mailer: Elog, Version 2.5.8-3
Content-type: TEXT/PLAIN; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
X-Elog-URL: http://njord................:8090/ikt/110
X-Elog-submit-type: web|elog


--

So the subject needs some change. In my example I left out what Elog inserts before
the subject I put in Elog.

Just for the fun, changed my old subject (in elog) to the one Mutt formatted it to:
Testing =?iso-8859-1?B?+Obl?=

And then I get what I want... ;)


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.

> 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

When I create a new logbook (I used an existing one as a template) elog  
does not works anymore...  
  
- The problem is on elog user's file.. It seems elogd can't read it  
anymore:  
  
Cannot open file arco.users: Success  
Please use your browser's back button to go back  
  
- Here are some informations:  
sparcserv:/usr/share/elog# ps U elog  
  PID TTY      STAT   TIME COMMAND  
 5165 ?        Ss     0:08 /usr/sbin/elogd -f /var/run/elogd.pid  
-c /etc/elog.conf -d /var/lib/elog -s /usr/share/elog -p 8080 -n  
sparcserv:/usr/share/elog# id elog  
uid=106(elog) gid=106(elog) gruppi=106(elog)  
sparcserv:/usr/share/elog# ls -lha arco.us*  
-rw-------  1 elog elog 1,8K 2005-03-24 12:21 arco.users  
-rw-r--r--  1 elog elog  473 2005-03-23 10:41 arco.users_bak  
sparcserv:/usr/share/elog#                  
  
giving the arco.users file chmod a+wr does *not* make it work ...  
 
re-chmod-ing to -rw-------  AND restarting the daemon solves the problem 
and everything works nice ...  
 
any idea?  
  
 
 

> Can conditional attributes be assigned as conditions?

Well, I guess the question was: "Can you implement this?" I'm sure that you
tried before.. (;-)

Yes, it is working now, I had to add some new code and fix a bug with AND'ed
conditions (via '&'). The new version is under CVS. Since you use Windows, you
have to wait for the next release.

> 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 
> field blank. I'm not sure if there's an easy way to change that attribute's name in 
> 100's of entries in 10's of logbooks, because I wouldn't want to try doing that by 
> hand.. Any ideas? (i'm no good at scripting something like that 4 sure)

find . -name "*a.log" -exec perl -pi -e 's|Work done at (dd/mm/yy hh:mm):|Work done at:|g' {} \;

Looks a bit cryptic, but searches for all *a.log files, and starts perl to replace
all occurences of "Work done at (dd/mm/yy hh:mm)" with "Word done at:". Better try
this first with a copy of your logbook. After you successfully changed that, you
have to modify the attribute list in elogd.cfg accordingly, like

Attirbutes = ..., Work done at, ...

Please note that after each manual modification of the logbook files, you have to
restart elogd.

> > I have been running ELOG on FreeBSD no problem for a year now,
> > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine 
> > with a few warnings (see attached logs).
> > But has issues with password files, now it shows message "Can't open 
> > passwords.pwd" for all my logbooks. It did convert the password files to 
> > xml format. I had a good hard look at file permissions and config file with 
> > no luck. So I went back a version and compiled 2.5.7-1 which works just 
> > fine with old password files. So something with XML & FreeBSD?...
> 
> Hard to say. The simplest would be if I could debug this.

Anything I could send you to help debug this?

> 
> > Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> > When I run a ./elogd -C http://elog.blah.here:88 it clones the config file 
> > just fine, also seems to copy over all logbook entries.
> > But once I look through them there's a fault with one of the fields it 
> > copies over, so entries never show up.
> > 
> > It should be:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh:mm):  1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> > 
> > But once cloned it looks like this:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh: m):  1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> > 
> > 
> > For some reason it looses the "m" so line 4 instead of having
> > "hh:mm" has "hh: m"
> 
> Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
> contains a ":". This character is not allowed in attributes. Unfortunately I did
> not document this (and even didn't know this until now... (;-) ). So you should
> use the new option
> 
> Type Work done at = datetime
> 
> this gives you at the entry mask fields for day/month/year/hour/minute to fill
> out, so you don't have to write it directly into the attribute. Another option
> would be to use 
> 
> Comment Work done at = Please enter as (dd/mm/yy hh:mm)
> 
> which just displays a comment below the attribute in the entry mask.
> 
> - Stefan

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 
field blank. I'm not sure if there's an easy way to change that attribute's name in 
100's of entries in 10's of logbooks, because I wouldn't want to try doing that by 
hand.. Any ideas? (i'm no good at scripting something like that 4 sure)

Thanks,
G.