I noticed a long url got hard-wrapped when I entered a long one, I patched 
the source code. I don't know if this was done intentionally, otherwise you 
might want to change this also.

diff elogd.c elogd.c.org 
4468c4468
<     rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
---
>     rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);

BTW, why is the editor window 20 rows by 76 columns ?
(20 is fixed in the source code, but 76 is the width-variable that is set 
hard to:

  /* set textarea width */
  width = 76;

Now I don't like both parameters. 20 is too long for my display (1024x768) 
and 76 is too short. Something dynamically would be cool, but a parameter 
somewhere in a config file would also be acceptable. (just a thought, makes 
it easier to upgrade)

When I make a new entry I get an email with 

   subject: New ELOG entry

But when I or someone else changes an entry I also get an email with a 

   subject: New ELOG entry

I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my 
programming capabilities so I enter this request.

Hi Stefan,

Many users have there email forward to Blackberry devices.  Although I 
wasn't aware, it appears the Blackberry has a limit (or maybe one was set) 
of how big the message can be (still checking for that though).

Previously, a modification was made that addressed the issue of slow ELOG 
response when saving the elog entry.   I think the change was for ELOG to 
generate one email and send to all the users designated to receive the 
notification.  This caused everyone to show up as "TO" addresses.

This change makes the Email header increase in size (length).  I guess the 
Blackberry counts the Header portion as part of the email size limit.

Any ideas?

Thanks, 
Eric

Another Question:  Could ELOG be configured to send notifications as a Blind 
Copy?  Just wondering if that would take care of the problem?

> Hi Stefan,
> 
> Many users have there email forward to Blackberry devices.  Although I 
> wasn't aware, it appears the Blackberry has a limit (or maybe one was set) 
> of how big the message can be (still checking for that though).
> 
> Previously, a modification was made that addressed the issue of slow ELOG 
> response when saving the elog entry.   I think the change was for ELOG to 
> generate one email and send to all the users designated to receive the 
> notification.  This caused everyone to show up as "TO" addresses.
> 
> This change makes the Email header increase in size (length).  I guess the 
> Blackberry counts the Header portion as part of the email size limit.
> 
> Any ideas?
> 
> Thanks, 
> Eric

I just noticed that the notifications I receive from your ELOG system, 
doesn't show anyone in the "TO:" section but myself.  Or is ELOG configured 
to only send myself a message?


> Another Question:  Could ELOG be configured to send notifications as a 
Blind 
> Copy?  Just wondering if that would take care of the problem?
> 
> > Hi Stefan,
> > 
> > Many users have there email forward to Blackberry devices.  Although I 
> > wasn't aware, it appears the Blackberry has a limit (or maybe one was 
set) 
> > of how big the message can be (still checking for that though).
> > 
> > Previously, a modification was made that addressed the issue of slow ELOG 
> > response when saving the elog entry.   I think the change was for ELOG to 
> > generate one email and send to all the users designated to receive the 
> > notification.  This caused everyone to show up as "TO" addresses.
> > 
> > This change makes the Email header increase in size (length).  I guess 
the 
> > Blackberry counts the Header portion as part of the email size limit.
> > 
> > Any ideas?
> > 
> > Thanks, 
> > Eric

When you do a find in elog, records per page (some crazy large number - for 
your forum logbook, display 57 entries seem to cause the problem, then 
select last year (1 years worth of logs),(don't select printable)

the results appear way off the screen (the message body looks fine, but the 
title, etc extend way off the screen).

Printable doesn't have this problem.

Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
port bindings, basically im running elog bound to port 81 and when i 
install the new RPM it refuses to bind to this port, i tried port 8080 and 
that worked fine

Any ideas ?

> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81

I haven't tried `stunnel` with elog, but as far as I read from various
sources, stunnel requires you to create an SSL certificate. In attachment,
you'll find a sample case for stunnel and smtp (port 25) + pop3 (port 110).
Hope this helps.

Reference: http://www.tldp.org/linuxfocus/common/sart/index.html