Is it possible to create a Link To command (ala Copy To, Move To) that
would allow you to reference an entry in another log book without copying it?
This would be handy as the info would be kept current in both log books.
My thought is that it would create a psuedo entry in the other log
book that pointed back at the originating log book entry (similar to a 
UNIX soft link)
/Tim

I am trying to unify several existing logbook collections that run on
seperate servers under a single server using groups.  For a top group, under
"[global topgroupname]", I would like to redefine the resource directory or
the logbook directory so that everything except for the .cfg is at it
original location.  However, it seems like "Resource dir" and "Logbook dir"
can not be redefined in the global section for specific groups.  Is it
possible to redefine these directories for each top group, or is it feature
that could be added?

I could probably do what I want with soft-links, but redefining the resource
dir just seems to be right way to do this.  (For one thing, I would like
different favicons for each group.)

> If my email host refuses to send the email (476 connections denied), we
> still get the message that the email has been sent - and no error message.
> 
> How do I or can I send authentication information to the email server?

This is not implemented right now, since the SMTP server at our institute does
not use authentication, so I could not test it. If you give me access to a
SMTP server with authentication, I could implement it.

If my email host refuses to send the email (476 connections denied), we
still get the message that the email has been sent - and no error message.

How do I or can I send authentication information to the email server?

> When I create a new logbook (I used an existing one as a template) elog  
> does not works anymore...  

Fixed in CVS.

> > If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> > Maybe that could be a solution?
> 
> Indeed it is. Works for all email programs I know. So I added that to elog, new
> version is committed to CVS. Let me know if it works for you.


Stefan! You are *THE MAN* :)

It works :)

You are indeed "speedy gonzales" ;)

Thank you very much!


Best regards
Michael 'very impressed' Husbyn

> If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> Maybe that could be a solution?

Indeed it is. Works for all email programs I know. So I added that to elog, new
version is committed to CVS. Let me know if it works for you.

> I implemented this, but found some problems. If I encode the subject like
> 
> Subject: =?ISO-8859-1?Q?ורז?=
> 
> it displays well unde MS Outlook, but not under Mozilla Thunderbird or pine,
> which both display the full text (including the ISO...). So it looks like
> there is no single solution which satisfies all mail programs. It should at
> least work for Outlook and Thunderbird, so if anyone has an idea please let me
> know.

If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
Maybe that could be a solution?

Best regards
Michael