I upgraded my system, including the version of Firefox.

I normally view the topic in Threaded Collapsed mode, right click on the entry I want to reply to, to open a new
Tab.  However, I made a mistake an opened a new Window, as the two 'open' modes in Firefox swapped around.
But no worry, I thought, made my reply as usual.

However, when refreshing the topic afterwards, seemingly randomly distributed throughout the topic were
additional lines, with the latest entry showing up emboldened (but not as a clickable link), and the only
difference being the ID number which showed as 0 (zero).

Deleting the reply only caused the previous reply to show up randomly etc.

In effect, the latest entry is (randomly?) scattered throughout the topic - even in between entries older than
any in that thread, so it's not individial entries in that thread showing up.

The only way to get rid of it was to erase the whole directory, and re-install from backup (which, as it was the
first entry since the new installation, wasn't painful).  It's been fine since - but only so long as I open a
thread in a new tab, and not in a new Window.

I guess the real question is just what is added to some file - perhaps the .cfg file? - that using a separate
window causes this behavioir?  Any whay only as a new window, and given how elog is supposed to work on many
computers, why on this stand-alone computer running two sets of the same browser?

It happened once before at the end of last year during a regression backwards owing to the newer computer
failing and turning back to an older one with older OS and older firefox, where I did the same thing (in
reverse).  As I didn't investigate at that time, I still have the mystery line showing up in that topic.

Sorry this is a bit rambling, but its very hard to describe!

> I upgraded my system, including the version of Firefox.
> [...]
> Sorry this is a bit rambling, but its very hard to describe!

A picture can say more than thousand words.
Can you reproduce this with a simple configuration?
If yes, can you attach the configuration, the *a.log files,
a description of what firefox version you're using and please:
some screenshots of "before" and "after"?

Thanks!
Andreas

> > I upgraded my system, including the version of Firefox.
> > [...]
> > Sorry this is a bit rambling, but its very hard to describe!
> 
> A picture can say more than thousand words.
> Can you reproduce this with a simple configuration?
> If yes, can you attach the configuration, the *a.log files,
> a description of what firefox version you're using and please:
> some screenshots of "before" and "after"?
> 
> Thanks!
> Andreas
That's odd, I cannot reproduce the problem today - except on the topic [logbook] it already exists on.
Yet nothing has changed.  
I've looked for hidden files, hidden control codes in the *a.log files...  this one had better be put on the
back burner until I can find a way to reproduce it (!).

I'm using Kerberos and SSL and experience problems with individual setting of "Login user =" for different logbooks.
Sometimes (not every time, but most times) the server crashes under the following condition:
When I login at one logbook and then change to a logbook, that has a restricted "Login user" list with my login
name not in it. It created the following GDB output:

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0x916b768, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:19793
19793         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;

Expected behaviour would be to show me the login page with the error message:
"you don't have access to this logbook".
This message is never shown for the attached configuration file.
If I remove the "Guest" commands for logbook "TestB" then elogd behaves properly.

For the moment I've just disabled "Login user" settings.

Regards
Andreas

Hello,

We use ELOG for many years and enjoy it's functions every day!

Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages

We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.

We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.

We had this error in the past and found out that the cause of this error lies in (network) time-outs.

Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?

Any replies are highly appreciated!

T I A !
 

Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?

Kind Regards
Andreas

> Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?

Hi Andreas,

Thank you very much for your reply. Thsi problem occurs also with the latest ELOG version 2.9.2

It would be nice if the timeout value(s) can be edited via the elogd.cfg file. Maybe this can be added in a new 
version.

Best regards,
Ron

Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log?