> however, I am not sure what elog checks for when doing the post through
> form. and the auto-submit script always failed and returns "200 EOF". i can
> get to the login part and grab form entry. its only the submittion failed.

What you can do is run the elog submit utility with the "-v" flag (verbose) and
grap the output. It's HTML code, but you should see any error message there.

> We currently have Elog postings mirrored on to a majordomo email list. 
> Invariably, people on this list reply to the listserv and not to the Elog. 
> Has anyone tried getting emails to a listserv to autoformat and register as
> proper elog entries.  Didn't see any mention of this in the docs or forums.

I personally use Elog *instead* a majordomo email list. You can either specify
a email list in the elogd.cfg file, or you can keep a list of users in the
password file with automatic email notifications, that's how this forum works
for example. But I don't know if you can give up your majordomo list.

Hi,

right now I'm testing Elog to use it as a task/todo-log for our small 
workgroup. What I saw so far looks very nice and I like it very much. 
Thanks for the good work.

Playing with all the configuration possibilities I have one issue:
I like to use the "Extendable options" but I can't combine them with 
the "Conditional attributes".

-- snip

Options Area = Area_1{1}, Area_2{2}, Area_51{3}
{1} Options Ressort = Res01, Res whatever, end so on
{2} Options Ressort = somthing else, fill in
{3} Options Ressort = Alien observation, Budget planning
Extendable options = Ressort

-- snip

The "Conditinal Attributes" do have the "Add Ressort" button and the elog-
entry is written with this new attribute. But the new attribute is not 
inserted into the config file.

Long time ago I last read C syntax but mabye the function 
add_attribute_option should take care of the prefix {n} in extendable 
options?

Or do I miss something in the configuration syntax? 

  Regards,

  David

I happened to find something interesting when trying my perl script. it hangs the
elog system with hand-crafted http header.

I also sent email with more detail on this. just want to make sure you are aware of
this.

Qiang

> > however, I am not sure what elog checks for when doing the post through
> > form. and the auto-submit script always failed and returns "200 EOF". i can
> > get to the login part and grab form entry. its only the submittion failed.
> 
> What you can do is run the elog submit utility with the "-v" flag (verbose) and
> grap the output. It's HTML code, but you should see any error message there.

Could you implemet and option 'admin menu' which gets displayed
when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
while the normal menu would not.

> I happened to find something interesting when trying my perl script. it hangs the
> elog system with hand-crafted http header.

This bug has been fixed in revision 1.524 of elogd.c available from CVS.

> Could you implemet and option 'admin menu' which gets displayed
> when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
> while the normal menu would not.

You can achieve the same via

Allow delete = <admin name>

Thanks to Recai Oktas, who encourage me to complete the Bulgarian
translation for the Debian elog package, the Bulgarian translation is
completed and attached.