Different behaviours to identical configuration of logbooks for email notification, posted by matthieu heller on Mon Jan 20 13:46:56 2020 
|
Dear,
I need to setup automatic email notification using direct send through a office365 smtp server.
This part worked without any issue after setting the right MX record as SMTP host.
As I am working on the configuration file while it is already use, I created a copy of the [GENERAL] logbook to make my tests called [GENERAL COPY] (see attachement and below for the config file).
Surprisingly I manage to send the email without errors using [GENERAL COPY] but not in [GENERAL]. In that case, I get this error message:
Error sending Email via <i>"cta####-####.mail.protection.outlook.com"</i>: 4.5.3 Recipients belong to multiple tenants [AM5EUR02FT024.eop-EUR02.prod.protection.outlook.com]
In that case, I was actually not sending the mail to a mailing list but to myself, a registered user.
Do you see any reason why two identical logbooks (except for the name) would behave differently ?
Best,
elogd.cfg:
[global]
port = 8090
SSL = 0
Self register = 0
Welcome Title = <html><font size=5>Welcome to the LST1 Elog server</font></html>
Main Tab = Main Logbooks page
URL = #######
SMTP host = cta####-####.mail.protection.outlook.com
SMTP port = 25
Use Email From = mailing-list@cta-####.org
Display Email recipients = 0
Email message body = 1
[GENERAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed = background-color:green
Cell Style Status Not Fixed = background-color:red
Cell Style Status Under Process = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd
[GENERAL COPY]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed = background-color:green
Cell Style Status Not Fixed = background-color:red
Cell Style Status Under Process = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd |
|
Different Top Groups or Groups have the same logbook name , posted by MATT TERRON on Tue Feb 2 04:01:21 2021
|
I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'? |
|
Difference between time and date formats, posted by David Pilgram on Wed Aug 29 22:44:39 2012
|
Hi,
I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats
Extract from my elog.cfg file:
Time format = %a %d %b %y
Date format = %d %b
Thread display = $Ticket: $System, $entry time. ($message id). $status
Preset text = [$date]
Prepend on reply = [$date] \n
I can point to places in the syntax doc where each of these lines are given.
As for the results, the thread display is (for example):
T00001: Computer, Wed 29 Aug 12. (1). Problem
However, what I get at the top of the text box in starting a new entry or replying to a previous one is
[Wed 29 Aug 12]
whereas I expected to get
[29 Aug]
Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference
I cannot see where I'm going wrong.
TIA
David. |
|
Deny option and Guest commands, posted by Janusz Szuba on Mon Jul 19 18:41:29 2021
|
Hi,
I have a logbook with guest access and guest can also enter a new entry (in config: Guest List Menu commands = New, Find, Select, Login). For other reason in a global section, I put
Deny New = account1, account2
This somehow invalidates Guest List Menu commands, since as guest I don't see New button anymore. Is this behaviour desired? Otherwise, I would need to move Deny option to plenty of individual logbook configs. Just to explain the reason, those accounts are set up to only read entries and not to create new ones. Or maybe you can suggest a different solution?
Best |
|
Deny Wildcards, posted by Neo on Wed Oct 8 15:10:25 2008
|
|
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ...
Allow New = admin1, admin2, admin3
Allow Edit = admin1, admin2, admin3
Deny New = *
Deny Edit = * |
Denial of access after failed import using invalid attributes, posted by soren poulsen on Wed Jun 17 03:46:31 2009
|
Hi,
A user tried to import a CSV file, which caused e-log to add a field called "date" to the list of attributes (and then crash). This caused the log-book to be blocked until someone (guess who) would go edit the elogd.cfg file and then trigger a reload.
1. suggestion : E-log should not crash in this case
2. suggestion: E-log should not allow invalid attributes to be added via CSV Import, which causes the log-book to be blocked.
For the time being, I will just "Deny import" (by the way, the doc says it is "Deny CSV import", but I think the syntax is "Deny import". Not really important.
I think this should be quite easy to reproduce.
Thanks a lot
Soren |
Denial of Service Vulnerability of elog 2.6.2-6, posted by Stefan Ritt on Wed Nov 8 13:59:52 2006
|
Dear ELOG users,
a denial of service vulnerability has been reported which affects all elog versions prior to 2.6.2-7. With a special request one can crash the elogd server, given that one has access either through a public read access or through an account. This vulnerability has been fixed in version 2.6.2-7. It is advised that all sensitive installations of ELOG are being updated.
Stefan Ritt |
|
Defunct daemons, posted by David Pilgram on Sat Mar 29 12:14:11 2014
|
Hi Stefan and Andreas
Yesterday I reported I had some issues with the latest elog: but now I can reproduce one.
elog 2.9.2-a738232
I started a new entry, and attached three pdf files. I did not get the problem of not seeing the png thumnbnail
this time, although that is annoying if you want/need to adjust the thumbnail image before submitting.
However, if I then look at the running processes, I have the following listed (ps -A)
23677 tty1 00:00:04 elogd
23809 tty1 00:00:00 elogd <defunct>
23825 tty1 00:00:00 elogd <defunct>
23847 pts/0 00:00:00 ps
23677 was when I started the elogd daemon, having killed off the previous daemon etc for test purposes.
23809 and 23825 appeared after a couple of pdfs were added (second and third ones to be precise). They can only
be killed off by killing off the original running daemon. It appears that attaching a second and further pdf
attachments to any entry generates an elogd <defunct> in the processes list, although attaching a jpg in the
middle of a list of pdfs didn't (but the next pdf did). This is happening while adding attachments, that is the
Submit button has yet to be pressed, so it seems to be generated when the pdf file is being processed for some
reason.
You can end up with quite a stack of these in the process list!
I never saw this behaviour with the previous version I was running, SVN2475 I think.
By the way, I still cannot send an attachment over to this server (showing a screenshot) without the 502 error. |
|