Re: read-only elog server, posted by Stefan Ritt on Mon Oct 23 16:15:06 2023
|
Use
Menu commands = List, Find, Help
to remove all command which let you create or edit entries (New, Reply, Edit, ...) |
Cannot send Emails, posted by John on Mon Oct 23 20:35:54 2023
|
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending
to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years
with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. |
|
Re: Cannot send Emails, posted by Stefan Ritt on Tue Oct 24 08:12:38 2023
|
ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince
your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.
Stefan |
|
Re: Restricting entries view by user, posted by Matteo Mannini on Tue Nov 7 22:07:24 2023
|
Dear Stefan,
thanks to the answer you gave to my colleague.
Now, attempting to follow your suggestion... If we will create several logbooks, one for each user, |
|
Re: Restricting entries view by user, posted by Stefan Ritt on Thu Nov 30 14:28:12 2023
|
Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict
edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.
Stefan |
|
user change under webserver authentication not recognized, posted by Frank Heyroth on Fri Jan 19 15:49:13 2024
|
Hi all,
I am using the Apache webserver authentication and redirection over http (not https). I have configured it 1:1 as described in the Adminguide.
In the elog.cfg I set Authentication = Webserver. |
|
How to not expose elog port when running under a reverse proxy, posted by Nicola on Mon Jan 22 08:22:33 2024
|
I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being
publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed,
but I cannot find how to configure the elog server to expose it only locally |
|
Re: How to not expose elog port when running under a reverse proxy, posted by Frank Heyroth on Mon Jan 22 20:50:50 2024
|
Hi,
as I understand right you can do this in the elogd.cfg via
Interface = 127.0.0.1 |