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

Fixed in CVS.

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

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

What you ask for is not possible due to internal reasons. The underlying database
does not support links. But what you can do is to reference a logbook entry with

elog :<loglook>/<id>

So I can reference your question with elog:Forum/1099. Some people make even
complete "summary" pages where they reference a whole set of other logbook entries like

Your question is at elog:Forum/1099
A script for thumbnail generation is at elog:Contributions/12
Demo entries: elog:Linux+Demo/14, elog:Linux+demo/1

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

Not easily. There is only a single logbook and resource directory inside elogd.
The reason is that these are constants which can be fixed during compile time.
The Debian package uses this extensively. So having multiple directories would
break that scheme.

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

I'm afraid you have to use soft links. The favicons you can define however via
the theme, which is a per-logbook option, so it would work in the [global
topgroupname] section as well.

> I am running 2.5.8-3 with the elogd.c 1.632.  I have attached the config
> file that I am using.   I have a top group "src", with logbooks "SRC
> Analysis" and "SRC Mail" in it.  These two logbooks share the same password
> file.  If one logs into one, I would like them to be not have to login to
> the other.  If I put the password file name under [global src], I get this
> behaviour, but the logbook selection page does not show my graphic or the
> locks by the logbook names (instead it has the Alt text "This logbook
> requires authentication."

Thanks for reporting this bug. I fixed it in the current CVS version.

> 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

It's hard to tell the problem from what you report. Have you tried the latest
release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
some problems with the password file in 2.5.8 versions prior to patch level 6.

> I have an question for you :o). Is there any solution to use the filtering 
> system with an match case solution ? Add a parameter or something else to 
> add a solution ? 

I added a paramet "case sensitive search" which does this. In addition, the
switch defines the default state of the "case sensitive" check box on the find
page. The new functionality will be contained in the next release.