Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 53 of 806  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  65785   Mon Mar 10 18:31:58 2008 Reply An Thaithaithan@gmx.deQuestionWindows2.7.3Re: still having email problems

mike cianci wrote:

Stefan Ritt wrote:

The transcript below looks all ok to me, so it's most likely that the email went to your Spam folder.

mike cianci wrote:

I no longer get an error message when I try to send an email (I get the "email sent" message) but the email never arrives.

Thank you (in advance) for any help.

My elog.log looks like:

10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} NEW entry #0
10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} Email from ELog@desktoppc to mike2.cianci@comcast.net, SMTP host desktoppc
10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} 220 smtp.comcast.net Microsoft ESMTP MAIL Service, Version: 6.0.2600.2180 ready at  Mon, 10 Mar 2008 07:05:31 -0800
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur}
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} HELO desktoppc
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 smtp.comcast.net Hello [192.168.1.101]
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} MAIL FROM: ELog@desktoppc
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.1.0 ELog@desktoppc....Sender OK
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} RCPT TO: <mike2.cianci@comcast.net>
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.1.5 mike2.cianci@comcast.net
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} DATA
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 354 Start mail input; end with <CRLF>.<CRLF>
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} Date: Mon, 10 Mar 2008 07:05:31 -0800
To: mike2.cianci@comcast.net
From: ELog <ELog@desktoppc>
User-Agent: Elog Version 2.7.3
Subject: New ELOG entry
Message-ID: <Centaur-23@desktoppc>
X-Elog-URL: http://localhost:8080/Centaur/23
X-Elog-submit-type: web|elog
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG - Test</title>
<link rel="stylesheet" type="text/css" href="http://localhost:8080/Centaur/default.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
</head>
<body>
<table class="frame" cellpadding="0" cellspacing="0">
<tr><td><table class="listframe" width="100%" cellspacing="0" cellpadding="0">
<tr><td class="title1">
A new ELOG entry has been submitted:</td></tr>
<tr><td class="attribhead">
<input type=hidden name="Author" value="mike">
<input type=hidden name="Instrument" value="Ginger">
<input type=hidden name="Category" value="Problem">
<input type=hidden name="Test" value="General">
<input type=hidden name="Subject" value="Test">
<input type=hidden name=browsing value=1>
Logbook:&nbsp;<b>Centaur</b>&nbsp;&nbsp;Message ID:&nbsp;<a href="http://localhost:8080/Centaur/23"><b>23</b></a>&nbsp;&nbsp;&nbsp;&nbsp;Entry time:&nbsp;<b>03/10/08 07:05:31</b>
</td></tr>
<tr><td><table width="100%" cellpadding="0" cellspacing="0"><tr><td nowrap class="attribname">Author:</td><td class="attribvalue">
mike&nbsp;</td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger&nbsp;</td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem&nbsp;</td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General&nbsp;</td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test&nbsp;</td>
</tr></table></td></tr>
</table><!-- listframe -->
</td></tr>
<tr><td class="messageframe"><p>This is a Test</p></td></tr>

</table><!-- show_standard_title -->
<center><a class="bottomlink" title="Goto ELOG home page" href="https://midas.psi.ch/elog/">ELOG V2.7.3-2058</a></center></body></html>

.
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.6.0  <Centaur-23@desktoppc> Queued mail for delivery
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} QUIT
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 221 2.0.0 smtp.comcast.net Service closing transmission channel

I checked for a spam filter and found none. I have also tried this on three different computers (with different email accounts) and still no luck.

 

Please use a valid email address for sender. All free email provider don't accept an invalid address, because of security against Spam problem.

Use Email From = xx@xxx.xx

 

  67282   Wed May 16 21:05:11 2012 Question NOCinatortgeis01@gmail.comQuestionWindows2.9.0ELOG 'Dashboard'

 First, I really appreciate this software. Thank you.

Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.

Doable?

Thanks!

  68224   Wed Jan 13 08:25:50 2016 Idea Tamas Galtgal@km3net.deInfoLinuxELOG V2.9.2-245Slackbot for ELOG

Dear all,

I just wanted to share a small script which I wrote to integrate our ELOG in Slack. This allows us to be notified immediately if there is a new logbook entry directly within the appropriate Slack channels. We're using ELOG V2.9.2-245 but if the log-file format has "Subject, Author, Type" in the header, it should work with any other version. I'm using Pyinotify for the file watch which relies on a Linux Kernel feature (merged in kernel 2.6.13) called inotify, so the script only works on Linux.

Here is the code: https://github.com/tamasgal/elog-slack

Cheers and thanks for ELOG!

Tom

Attachment 1: elog-slack.png
elog-slack.png
  68225   Wed Jan 13 08:37:42 2016 Reply Tamas Galtgal@km3net.deQuestionLinuxELOG V3.1.0-241Re: Monitoring a logbook for changes

I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.

Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224

Johan Forsberg wrote:

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

 

  68228   Wed Jan 13 17:04:34 2016 Reply Tamas Galtgal@km3net.deQuestionLinuxELOG V3.1.0-241Re: Monitoring a logbook for changes

I just noticed that there are multiple messages per file, so I have to adapt the parser. I'll update this thread when I'm done!

Johan Forsberg wrote:

Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.

Thanks for the pointer!

Tamas Gal wrote:

I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.

Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224

Johan Forsberg wrote:

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

 

 

 

  68230   Wed Jan 13 18:37:32 2016 Reply Tamas Galtgal@km3net.deQuestionLinuxELOG V3.1.0-241Re: Monitoring a logbook for changes

Where is this feature documented?

Stefan Ritt wrote:

You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.

 

  68232   Wed Jan 13 19:13:47 2016 Reply Tamas Galtgal@km3net.deQuestionLinuxELOG V3.1.0-241Re: Monitoring a logbook for changes

I'm probably too tired or I don't know, but of course I looked at the user's guide and the admin's guide but did not found anything about this ;-) Is there another documention which I missed somehow?

Stefan Ritt wrote:

In the documentation of course :-)

Tamas Gal wrote:

Where is this feature documented?

Stefan Ritt wrote:

You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.

 

 

 

  68234   Wed Jan 13 19:26:35 2016 Reply Tamas Galtgal@km3net.deQuestionLinuxELOG V3.1.0-241Re: Monitoring a logbook for changes

OK thanks I'll check that out. I did not configure ELOG by myself, I only use it and wrote the Slack plugin ;-)

Stefan Ritt wrote:

You look here: http://midas.psi.ch/elog/config.html and scroll down to "Execute New". I wonder how you ever could run elog without looking at that page.

Tamas Gal wrote:

I'm probably too tired or I don't know, but of course I looked at the user's guide and the admin's guide but did not found anything about this ;-) Is there another documention which I missed somehow?

Stefan Ritt wrote:

In the documentation of course :-)

Tamas Gal wrote:

Where is this feature documented?

Stefan Ritt wrote:

You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.

 

 

 

 

 

ELOG V3.1.5-3fb85fa6