Thank you for responding.

I thought I provided the command at the end of the note:

/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"

This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text.  The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.

For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.

Sorry for forgetting these details:  bash shell; linus version 2.6.32-696.el6.x86_64

Hi Daniel,

I agree: it should. And it does in my case; it works perfectly fine for my logbooks. Maybe you should have a closer look for special characters in you configuration? Otherwise I don't know why it does not work for you.

If you haven't figured it out already you would need to send a working snippet of your logbook configuration together with a minimal collection of entries that are filtered wrongly.

Cheers, Andreas

Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?

Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) .  Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this.  Can you see what it is?  Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?

[global]

.

Suppress Email to users = 1
.

[Notebook]

.

Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...

.

{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...

{3} Email Category TDAQ =
.

Use Email Subject = Elog Notice: $subject
 

Command:  /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"

Hi Daniel,

you're the first one reporting about this virus. We have different virus checkers here at our lab and none of them triggered. So I guess it is a false alarm.

Best,

Stefan

Hello.

Today I noticed that when I use category filter in the top, right of Elog I got different results, that depends on that if I select Category and Subcategory or just Subcategory option.

What I mean.

1. When I select category Software (in Polish "Oprogramowanie") and subcategory Antywirus I got results that have only this subcategory specified (screenshot Category-Software_and_Subcategory-Antywirus.png)
2. But when I write by myself Antywirus (which is subcategory of Software) in subcategory option (category leave as default), then I got results that have this, and other subcategories specified (screenshot Subcategory-Antivirus.png). 

In my opinion in first example Elog shoud also displays all entries that have Antywirus subcategory specified. Not only when it is the only subcategory.

Sorry, for my english, but I have hope that you can understand what I mean.

Daniel

Hello.

Today I wanted to download latest elog version, and got information from Eset Endpoint Antyvirus, that downloaded file has trojan horse "Generic.GQWFFXB".

It this false positive alarm?

Daniel

One possibility is to run elog in non-SSL mode and put an Apache server in front of it. The Apache server can then do the SSL communication, and forward all requests to elog in plain text (non-SSL). This has been proven to work with large attachments, actually that's the way I use it.

I didn't find time to debug the SSL problem. If anybody is interested in doing so, the relevant code is in function server_loop() around line 30015 (SSL_read()).

Stefan