> Is it possible to add one more "text entry" field ?

I guess you mean the main body text, which is multi-line. No, this is not
possible right, now, but I added your vote to the wishlist istem "Multi-line
attributes".

Your guess is correct. I would like to have that feature in ELOG.

Thanks

> > Is it possible to add one more "text entry" field ?
> 
> I guess you mean the main body text, which is multi-line. No, this is not
> possible right, now, but I added your vote to the wishlist istem "Multi-line
> attributes".

You can do this by defining groups. For this forum I did

Group Demo = Linux Demo, Database
Group Discussion = Forum, Config Examples, Contributions, Vulnerabilities

where each name on the right side of the equal sign is an individual logbook.

• you need to copy your logbooks into the "logbooks" directory.
• you need to copy your elog.cfg logbook config file to the new elog folder and reference it at start-up (something like "elogd -c /usr/local/elog/elogd.cfg ...")

Some people modify other stuff (CSS, java scripts) but if you had you would know what you did.

If the old ELOG was a 2.x version and the new is 3.x, then on the first start-up all logbook data files are copied into sub-folders for each year.
This is only done (automatically) during the first start-up, afterwards you can not use a 2.x version anymore (you won't want that anyway).

From your point of view that request is reasonable, but the reason of having mxml in a separate top level directory is that I use it in many different projects. If I would keep a copy of mxml in each project, I would have to update all of them manually if there is a bug. On the other hand the code of mxml changes very seldom. If you look at the history, it got ~5 changes last year, while elog itself had hundreds. And since I do not change the API, a bugfix in mxml should be to the benefit of all elog versions. It is like with other projects which depend on a number of packages. Like if you install Apache for example, you need a certain version of OpenSLL, a certain version of libcrypt, and so on.  So think of mxml like another package you have to combine with elog.

•  You can add the "Move to = B" command in logbook A.
• Then you add "select" in "List Menu commands = ..., select, ...".
• Now you "Find" all entries of the type you want (for convenience choose "Display 9999 entries per page").
• You press "toggle all" and then "Move to B"

> For authentication via the Windows IIS I have "basic authentication" with no TLS encryption required - I'm 
> not sure if that meets the provider's "SMTP authentication" requirement.  When I was using the previous version 
> of ELOG (sorry, I did not note the version number) the username was encrypted along with the password.  With 
> the 2168 build, the password is still encrypted but the usernamer is not; should the password be in "plain 
> text" as well?  

I changed only the screen output. The username is printed not not encrypted, to be able to check it by eye. The 
username sent over the network is and was always encrypted.

The only clue I have is to compare the network traffic you get with an email client (outlook, thunderbird ??) 
with the network traffic you get from elogd. To monitor the traffic, I use normally WireShark (formerly Ethereal, 
www.wireshark.org). You have to filter for "tcp.port == 25" which is SMTP, then capture your traffic, right-
click on it and select "Follow TCP stream". The result you see in the attachment. The strings produced by elogd 
are pink, the strings from the SMTP server are blue. In my case I don't have authentication (our SMTP server does 
not support this). In you case, you have to compare the traffic from a functioning email client with elogd.

> 
> missing '.' in emails
> -----------------------
> 
> A dot '.' at the beginning of a line is not transmitted via email.
> It is stored in the entry properly though.
> 
> Test:
> ./There is a dot just before '/There...'
> 
> Greetings, Heiko

Here is what I got as email:

Test:
./There is a dot just before '/There...'

So I guess you mean ONLY a dot at the beginning of the line. In the email 
SMTP protocol, at lonely dot at the beginning of the line means "end of 
message" and the mail server stops by that. I checked my mail program and 
found out that it converts a single dot into two dots at the beginning of the 
line. I have to implement this in elgod.c. Thanks for pointing out this 
problem.