Hi. I have a same problem... It works well with other browsers, like firefox and internet explorer, but not with safari (with and without keep-alives). 

The demo logbook in the link works fine with safari, though. 

Thanks.

Tsuguo

Thanks for reporting this bug. I finally found the reason and fixed it in revision 2191. I made a new release 2.7.6 which contains all the collected bug fixes from the last few months.

Hi,

I am trying the Preset text option from the documentation: like:

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

I have two questions:

1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.

2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just  one line in my e-log. I would really like a multi-line form.

Soren

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

 Dear Soren,

Just use HTML (and call the file network.html to remember).

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

Without path, the file must reside in the "scripts" subdirectory.

For the multi-line form, it depends how you want to format your elog entry. If you format in "plain", the simple line breaks are sufficient. If you format in HTML, your preset file must be in HTML as well, so a line break has to be a <br> tag. If you format in ELCode, a simple line break again would be ok. 

Attributes = Author, Type
Options Type = Network check{1}, System check{2}

{1} Preset text = network.txt
{2} Preset text = system.txt

 Thanks for the hints on the "scripts" dir.  For the formatting, that's clear. I started with the sample "network.txt" file from the doc and the default encoding (HTML), so that did (of course) not render correctly (before inserting a few tags).

Soren

Great software.

Okay, so I've done my reading through the forum and got a couple of nuggets along the way but I am still unable
to get the e-mail function to work.  I am using Windows IIS to make an SMTP virtual server to shimmy around the
IT firewall.  That appears to work as I can see the response from the external SMTP server while running elogd
with the -v flag.  The elogd -v details are below:  

Email from xxxxxxxxxxxx@xxxxxxxxxxxx.com to xxxxxx.XXXXXXX@XXXXX.com,XXXXX.XXXXX X@XXXXX.com, SMTP host
XXXXXXXXXXXXXX.XXXX.XXXXX.com: 
220 smtp.xxxxx.com Microsoft ESMTP MAIL Service, Version: 6.0.2600.2180 ready at   Mon, 26 Jan 2009 10:56:35 -0500 
EHLO xxxxxxxxxxxxxx.xxxx.xxxxx.com 
250-smtp.xxxxx.com Hello [xxx.xxx.xxx.xxx] 
250-AUTH=LOGIN 
250-AUTH LOGIN 
250-SIZE 2097152 
250-PIPELINING 
250-DSN 
250-ENHANCEDSTATUSCODES 
250-8bitmime 250-BINARYMIME 
250-CHUNKING 250-VRFY 
250 OK AUTH LOGIN 
Username: 
xxxxxxxxxxxx@xxxxxxxxxxxx.com 
Password: cm9jaGVsb2dib29r 
535 5.7.3 Authentication unsuccessful 
==== Return ================================  

From the SMTP server response it is not logging in, but I don't know why.  I can log in to the webmail app with
the username/password provided to ELOG, but it doesn't appear to work through ELOG. The SMTP provider includes
the following info to setup e-mail accounts via SMTP: "Please note: To send e-mail using the SMTP-Server,
activate SMTP Authentication. Please do not use the Secure Password Authentication (SPA) option. Optionally,
port 587 can also be used in addition to the default port (25) RFC 2476." 

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 can provide you with a username/password for the SMTP provider I'm using if that will help.  Please send me a
separate e-mail and I will reply with the information.  

Thank you,  

Topher Congdon

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