I just tried with IE8 (don't have IE7 installed any more), and it looked to me like this has been fixed there. So this will get less a problem in the future. If people are stuck to IE7, they can made your modification themselves in the CSS file, so I guess I won't change the distribution for the moment.

> I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> next email received was due to the third entry of this thread.

Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):

1st reply to your entry.

1st reply edited.

> > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> > next email received was due to the third entry of this thread.
> 
> Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> 
> 1st reply to your entry.
> 
> 1st reply edited.

I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem 
with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay 
between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML, 
your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more 
likely.

> > > > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> > > > next email received was due to the third entry of this thread.
> > > 
> > > Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> > > 
> > > 1st reply to your entry.
> > > 
> > > 1st reply edited.
> > 
> > I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem 
> > with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay 
> > between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML, 
> > your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more 
> > likely.
> Hi Stefan,
> 
> I confirm that this is a slow internet line, so that explains the Proxy Error.  
> 
> Maybe I should just keep my head down on threads where people use html coding ;-)
> 
> Did you receive two emails to my entry 66677?  I only received one.
> 
> I only received one email to your posting 66680 - the first entry, not the edited version.

I checked my email server and found that the second message really went though it. But then I realized that there is indeed the "Message-
ID:" in the email header (which I completely forgot in meantime). So maybe George Paplexis is right in that some mail 
server/forwarder/receiver ignore a second email if it has the same ID. That would mean however that I have to introduce a "revision 
number" for elog entries, which gets incremented on each edit and gets attached the the message-ID, so that it becomes unique again. 
That's quite some work and has to wait a bit.

If you download the standard package, it installs a demo logbook on your computer which you can use as a personal logbook. It uses port 8080 by default, although this can be changed. Then only thing you need to do is to make sure that port 8080 is blocked on your firewall. Read your OS documentation on how to set-up and use a firewall. Once you block port 8080, the data cannot be accessed from outside your laptop. 

You can start the elogd daemon even when you don't have internet access, and access your database locally under http://localhost:8080. For changing the title of a logbook, please read the documentation. 

Dear ELOG users,

this is to announce an important security update. As proposed by Lukasz Olejnik (CERN/PSNC), ELOG has now switched to strong encryption of password. So everybody concerned in security is advised to update to the new version 2.8.0. Existing password files for Windows users and Linux users not using HAVE_CRYPT are automatically converted. Those installations which used HAVE_CRYPT in the past under Linux have to ask their users to re-enter their password (via the link "Forgot password") after the upgrade to version 2.8.0.

Best regards,

  Stefan Ritt

I just realized that the command line elog utility did not yet use the new encryption. So automatic elog submissions using passwords are broken in version 2.8.0. I made an intermediate version 2.8.0-2 which fixes that. However you only need to update it if you use the elog utility and have problems with the 2.8.0 version.