Then the answer is no. 

The first thing you can do with "Guest menu commands", where you enable only those commands which can't change or delete entries. The second thing you can only do if you put your entries into two separate logbooks, a public and a private one. 

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

Have you started the server with the "-x" flag as written in the documentation? 

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

 Thanks a lot for replying despite the heat. Yes, I executed with the "-x" flag.

It is just a quoting problem, I guess. This line works:

Execute new = echo New message with ID $message id of type $type from $long_name on $remote_host >> /tmp/elog.log

It evaluates to:

SHELL "echo New message with ID 24706 of type elogtype from Soren Poulsen on 137.138.22.11 >> /tmp/elog.log"
 

So next step is to replace "new" with "edit" and "delete".

That works as well.

Soren

 There is an firefox addon "It's all text" that allows you to call your own editor for all textarea fields in the browser.

If you then choose "plain" or "ELCode" encoding in ELOG for a new entry or to modifiy an existing entry, you can use your favourite editor to edit the entry by an new "EDIT" button associated with the textarea input field. It works simply by temporary files.

Not really a "drop-in" replacement, but similar.

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)

How can I make this line work ?

Soren

There is sometimes a problem with substitutions like "Execute delete = echo $message id".

It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.

In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.

Soren

This is not possible at the moment. Sounds to me more like a calendar function. What you could do however is to define an attribute of type "datetime", which you can populate with the expiration date. Then you can do a search to look for entries which are past the expiration date. But you have to do that manually like once per day or so. 

Thank you for your reply and the tip.

People can allways use another app (mail) for this, it would be nice,nothing more.