> 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.

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.

I just submitted a reply to elog:847 (the reply is elog:853).
Normally the thead containing the reply should now be listed as
the top thread.  Instead only the original message of the thread
(elog:820) is listed but the remaining messages in the thread are not 
listed.  It seems the problem is that for elog:820 the 'reply to this'
header is missing.  And elog:820 and elog:824 are the same messages
except that for elog:824 the subject is missing.  Actually ALL attributes
for elog:824 are missing.

I guess you could fix things up if you:
- add 'reply to this: 823' to elog:820
- remove entry elog:824

> 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 implement a 'hide attribute' and 'sort attribute' config option?

I implemented it as 'hidden attributes = <list>' and 'sort attributes'.

> > Could you implement a 'hide attribute' and 'sort attribute' config option?
> 
> I implemented it as 'hidden attributes = <list>' and 'sort attributes'.

'sort attributes' sorts the logbook entries when they are displayed.  Or?

What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
should be listed first, as they are required for this bibtex entry type.
Is it possible with the current elogd version to also sort (rearrange) the 
attributes in the entry mask?  If yes, how?  

Thanks for your time.

> 'sort attributes' sorts the logbook entries when they are displayed.  Or?

Right

> What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
> selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
> should be listed first, as they are required for this bibtex entry type.
> Is it possible with the current elogd version to also sort (rearrange) the 
> attributes in the entry mask?  If yes, how?  

Attributes are shown in the order you specify them in the config file, so what about

Attributes = Entry type, Author, Journal, Title, Year     ???

> > 'sort attributes' sorts the logbook entries when they are displayed.  Or?
> 
> Right
> 
> > What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
> > selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
> > should be listed first, as they are required for this bibtex entry type.
> > Is it possible with the current elogd version to also sort (rearrange) the 
> > attributes in the entry mask?  If yes, how?  
> 
> Attributes are shown in the order you specify them in the config file, so what about
> 
> Attributes = Entry type, Author, Journal, Title, Year     ???

Because for 'Entry type'='InProceedings' one needs:
'Author', 'Title', 'Booktitle', 'Year', 'Volume', 'Number'.
So, depending on the entry type that was chosen the entry mask should change,
with the required fields first and the not valid fields should not be shown
at all, which can nicely be done with the 'hidden attributes' config option.
Only the sorting (of the entry mask!) is missing! :)