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 !
 

 Thanks a lot!
I love this program, there is no end of the possibilities.

/UlfO

Start page = ?Status=Open|Ongoing

 OK, Thanks!
Is it possible to use Start Page with more than one parameter?
For instance if I want to filter on two filter options at the same time, like Status= Open and Status=Ongoing

Sure. Lets assume you have a "Status" attribute, which can be "open" and "finished", then you need

Options Status = open, finished
Quick Filter = Status
Start page = ?Status=open 

The quick filter gives you a drop-down box where you can switch quickly between "open" and "finished", while the "Start page" automatically filters for "open".

Hi,

Is it possible to have a default filtered view in E-log?

Lets say we have a record with status finished on one attribute.

Is it possible to have a default list view that just shows records with this status?

Forget the previous post:
I cannot reproduce the problem with the latest version of elogd (2.9.2-2475).

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