Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 183 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  69060   Mon Nov 18 16:58:21 2019 Idea Roger Kaltroger.kalt@psi.chInfoLinux3.1.4Example scripts how to migrate or combine logbooks

Attached the shell scripts using awk and sed how I have migrated two separated logbooks into one single and how I re-adjusted certain attributes.

Attachment 1: run_modif.sh
#!/bin/bash
# KR84, 28.10.2019

# the input files are the exported XML files from ELOG -> Finden


# search in XML for sring between <DATE> and </DATE>
# and replace with: <DATE> and </DATE><When> and </When>
echo "converting export_rf.xml ..."
cat ./export_rf.xml | 
    sed 's/<Personnel\(.*\)Personnel>/<Author\1Author>/g' |
    sed 's/<DATE\(.*\)DATE>/<DATE\1DATE>\n\t\t<When\1When>/g'   |
    sed 's/<Subject>\(.*\)<\/Subject>/<Title>\1<\/Title><Entry_Type><\/Entry_Type>/g' |
    sed '/<Machine>SwissFEL<\/Machine>/ {N;N; s/<Machine>SwissFEL<\/Machine>.*<Domain>OBLA<\/Domain>.*<Section>TRFCB/<Machine>OBLA<\/Machine>\n\t\t<Domain>All<\/Domain>\n\t\t<Section>TRFCB/g}'  |
    sed 's/<When>Mon, /<When>/g'                          |
    sed 's/<When>Tue, /<When>/g'                          |
    sed 's/<When>Wed, /<When>/g'                          |
    sed 's/<When>Thu, /<When>/g'                          |
    sed 's/<When>Fri, /<When>/g'                          |
    sed 's/<When>Sat, /<When>/g'                          |
    sed 's/<When>Sun, /<When>/g'                          |
    sed '/<When>.*<\/When>/{s/ Jan 20/.01./g}'                    |
    sed '/<When>.*<\/When>/{s/ Feb 20/.02./g}'                    |
    sed '/<When>.*<\/When>/{s/ Mar 20/.03./g}'                    |
    sed '/<When>.*<\/When>/{s/ Apr 20/.04./g}'                    |
    sed '/<When>.*<\/When>/{s/ May 20/.05./g}'                    |
    sed '/<When>.*<\/When>/{s/ Jun 20/.06./g}'                    |
    sed '/<When>.*<\/When>/{s/ Jul 20/.07./g}'                    |
    sed '/<When>.*<\/When>/{s/ Aug 20/.08./g}'                    |
    sed '/<When>.*<\/When>/{s/ Sep 20/.09./g}'                    |
    sed '/<When>.*<\/When>/{s/ Oct 20/.10./g}'                    |
    sed '/<When>.*<\/When>/{s/ Nov 20/.11./g}'                    |
    sed '/<When>.*<\/When>/{s/ Dec 20/.12./g}'                    |
    sed 's/ +0100<\/When>/<\/When>/g'                                     |
    sed 's/ +0200<\/When>/<\/When>/g'                                     > export_rf_modified.xml



#    sed 's/ Jan 20/.01./g'                              |
#    sed 's/ Feb 20/.02./g'                              |
#    sed 's/ Mar 20/.03./g'                              |
#    sed 's/ Apr 20/.04./g'                              |
#    sed 's/ May 20/.05./g'                              |
#    sed 's/ Jun 20/.06./g'                              |
#    sed 's/ Jul 20/.07./g'                              |
#    sed 's/ Aug 20/.08./g'                              |
#    sed 's/ Sep 20/.09./g'                              |
#    sed 's/ Oct 20/.10./g'                              |
#    sed 's/ Nov 20/.11./g'                              |
#    sed 's/ Dec 20/.12./g'                              |




# search in XML and add offset to all IDs because they shall not overlap when merged.
echo "converting export_llrf.xml ..."
cat ./export_llrf.xml           | sed 's/<Subject>\(.*\)<\/Subject>/<Entry_Type><\/Entry_Type>\n\t\t<Status><\/Status>\n\t\t<Title>\1<\/Title>\n\t\t<Inv_ID><\/Inv_ID>/g' > export_llrf_modified1.xml
cat ./export_llrf_modified1.xml | awk -F'\t\t<MID>|</MID>||' '{ if ($2!="") {print "\t\t<MID>"$2+2016"</MID>"} else { print $1} }' > export_llrf_modified2.xml
cat ./export_llrf_modified2.xml | awk -F'\t\t<REPLY_TO>|</REPLY_TO>||' '{ if ($2!="") {print "\t\t<REPLY_TO>"$2+2016"</REPLY_TO>"} else { print $1} }' > export_llrf_modified3.xml
cat ./export_llrf_modified3.xml | awk -F'\t\t<IN_REPLY_TO>|</IN_REPLY_TO>||' '{ if ($2!="") {print "\t\t<IN_REPLY_TO>"$2+2016"</IN_REPLY_TO>"} else { print $1} }' > export_llrf_modified.xml

rm -rf ./export_llrf_modified1.xml ./export_llrf_modified2.xml ./export_llrf_modified3.xml 

cat ./export_llrf_modified.xml | 
    sed '/<Machine>SwissFEL<\/Machine>/ {N;N; s/<Machine>SwissFEL<\/Machine>.*<Domain>Test Systems<\/Domain>.*<Section>TRFCB/<Machine>OBLA<\/Machine>\n\t\t<Domain>All<\/Domain>\n\t\t<Section>TRFCB/g}'  |
    sed 's/<When>Mon /<When>/g'                           |
    sed 's/<When>Tue /<When>/g'                           |
    sed 's/<When>Wed /<When>/g'                           |
    sed 's/<When>Thu /<When>/g'                           |
    sed 's/<When>Fri /<When>/g'                           |
    sed 's/<When>Sat /<When>/g'                           |
    sed 's/<When>Sun /<When>/g'                           |
    sed 's/-Jan-/.01./g'                              |
    sed 's/-Feb-/.02./g'                              |
    sed 's/-Mar-/.03./g'                              |
    sed 's/-Apr-/.04./g'                              |
    sed 's/-May-/.05./g'                              |
    sed 's/-Jun-/.06./g'                              |
    sed 's/-Jul-/.07./g'                              |
    sed 's/-Aug-/.08./g'                              |
    sed 's/-Sep-/.09./g'                              |
    sed 's/-Oct-/.10./g'                              |
    sed 's/-Nov-/.11./g'                              |
    sed 's/-Dec-/.12./g'                              |
    sed 's/ +0100<\/When>//g'                                     |
    sed 's/ +0200<\/When>//g'                                     |
    sed 's/<\/When>/:00<\/When>/g'                      |
    sed 's/<When>-:00<\/When>/<When><\/When>/g'                    > export_llrf_modified_datetime.xml

echo "export_llrf_modified_datetime.xml need manual edit for empty <When></When>"
Attachment 2: generate_import_llrf_fwd.sh
#!/bin/bash
# KR84, 28.10.2019

# generate emtpy auto-fwd text for LLRF for 3100 entries and offset of 2000
echo "generated import_llrf_fwd.xml"
echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?>" > import_llrf_fwd.xml
echo "<ELOG_LIST>" >> import_llrf_fwd.xml

declare -i ID
declare -i IDNEW

for ID in {1..3013}
do
    IDNEW=$ID+2016

    echo -e "\t<ENTRY>" >> import_llrf_fwd.xml
    echo -e "\t\t<MID>${ID}</MID>" >> import_llrf_fwd.xml
    echo -e "\t\t<DATE>Mon, 28 Oct 2019 20:00:00 +0200</DATE>" >> import_llrf_fwd.xml
#    echo -e "\t\t<DATE>28.10.2019 20:00:00</DATE>" >> import_llrf_fwd.xml
    echo -e "\t\t<ATTACHMENT></ATTACHMENT>" >> import_llrf_fwd.xml
    echo -e "\t\t<ENCODING>HTML</ENCODING>" >> import_llrf_fwd.xml
    echo -e "\t\t<When>28.10.2019 20:00:00</When>" >> import_llrf_fwd.xml
#    echo -e "\t\t<When>1572289200</When>" >> import_llrf_fwd.xml
    echo -e "\t\t<Author>Kalt Roger (KR84)</Author>" >> import_llrf_fwd.xml
    echo -e "\t\t<Machine>SwissFEL</Machine>" >> import_llrf_fwd.xml
    echo -e "\t\t<Domain></Domain>" >> import_llrf_fwd.xml
    echo -e "\t\t<Section></Section>" >> import_llrf_fwd.xml
    echo -e "\t\t<System></System>" >> import_llrf_fwd.xml
    echo -e "\t\t<Subsystem></Subsystem>" >> import_llrf_fwd.xml
    echo -e "\t\t<Subject>Automatic forward</Subject>" >> import_llrf_fwd.xml
    echo -e "\t\t<TEXT>&lt;meta http-equiv=&quot;refresh&quot; content=&quot;0; URL=&apos;https://elog-gfa.psi.ch/SwissFEL+RF/${IDNEW}&apos;&quot; /&gt;</TEXT>" >> import_llrf_fwd.xml
    echo -e "\t</ENTRY>" >> import_llrf_fwd.xml
done

echo "</ELOG_LIST>" >> import_llrf_fwd.xml

  69063   Fri Nov 22 02:55:50 2019 Warning John S. Haggertyhaggerty@bnl.govBug reportMac OSX3.1.4Trouble on Catalina

I decided to rebuild elog 3.1.4 in Catalina (MacOS 10.15.1), XCode 11.2.1.  As in previous builds, I needed to add to the Makefile pointers to openssl:

CFLAGS += -I/usr/local/opt/openssl/include

LIBS += -L/usr/local/opt/openssl/lib

The make builds cleanly, no errors, no warnings.  After make/make install, elogd segfaults immediately.  I saw the same behavior with the version in gitlab.  I kept my (very) old build and was able to make install it without recompiling and it still works.

I'll crack out the debugger when I have a chance to get more information, but has anyone else seen this problem?  

  69066   Mon Nov 25 16:25:21 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: Trouble on Catalina

The Makefile is kind of obsolete, I switched to CMake. So the Makefiel is mostly there as backup. To compile elog, do

elog$ mkdir build; cd build
elog/build$ cmake ..
elod/build$ make install

that should also find your openssl library, since CMake is more clever.

I personally have not yet switched to MacOS Catalina, since I have too many 32-bit programs running there and wait until all of these get updated. Only then I will be able to test elog under Catalina.

Stefan

John S. Haggerty wrote:

I decided to rebuild elog 3.1.4 in Catalina (MacOS 10.15.1), XCode 11.2.1.  As in previous builds, I needed to add to the Makefile pointers to openssl:

CFLAGS += -I/usr/local/opt/openssl/include

LIBS += -L/usr/local/opt/openssl/lib

The make builds cleanly, no errors, no warnings.  After make/make install, elogd segfaults immediately.  I saw the same behavior with the version in gitlab.  I kept my (very) old build and was able to make install it without recompiling and it still works.

I'll crack out the debugger when I have a chance to get more information, but has anyone else seen this problem?  

 

  69076   Thu Dec 19 16:28:06 2019 Warning Devin Bougiedab66@cornell.eduBug reportLinux | Windows | Mac OSX | All | Other3.1.4text wrapping broken in firefox
When creating new logbook entries, recent versions of firefox somehow ignore the message width setting.

For example, configure a logbook with:
Message Width = 76
Message Height = 20

Then, create a new plain text entry that contains very long lines.  The text entry box is the correct size, but once you hit submit and view the full display of the message, it is not wrapped properly.  The summary display is wrapped properly, but not the full display.

We've only found this to be a problem with recent versions of firefox.  Chromium, Safari, and old versions of firefox behave properly.
  69077   Thu Dec 19 16:40:10 2019 Reply Devin Bougiedab66@cornell.eduBug reportLinux | Windows | Mac OSX | All | Other3.1.4Re: text wrapping broken in firefox
As an example, I created this same entry in the demo logbook using Safari.  As you can see there, the message is wrapped at the width that I set the text entry box.

https://elog.psi.ch/elogs/Linux+Demo/9

> When creating new logbook entries, recent versions of firefox somehow ignore the message width setting.
> 
> For example, configure a logbook with:
> Message Width = 76
> Message Height = 20
> 
> Then, create a new plain text entry that contains very long lines.  The text entry box is the correct size, but once you hit submit and view the full display of the message, it is not wrapped properly.  The summary display is wrapped properly, but not the full display.
> 
> We've only found this to be a problem with recent versions of firefox.  Chromium, Safari, and old versions of firefox behave properly.
  69079   Mon Jan 20 13:46:56 2020 Question matthieu hellermatthieu.heller@unige.chQuestionLinux3.1.4Different behaviours to identical configuration of logbooks for email notification

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

Attachment 1: 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


[CAMERA]
Theme = default
Comment = LST1 Camera ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = ECC, TIB, CACO, EVB, UCTS, test, Fibers, Camera, ClusCo, DATA, CACO/ClusCO, Calib box, Camera Server, Monitoring, Backplane, Observation, Daily calibration, Dragon, Operation, Trigger Mezzanine, PDB, CDTS, Switches, Cooling
Options Category = General, Hardware, Software, Network, Other, Weather conditions
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, Category
Required Attributes = Author, Type
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = camera
Password file = camera.pwd

[AMC]
Theme = default
Comment = LST1 AMC ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, Issues, pointing calibration
Options Category = General, Hardware, Software, Network, Other
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, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = amc
Password file = amc.pwd

[ENERGY]
Theme = default
Comment = LST1 Energy ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, Issues
Options Category = General, Hardware, Software, Network, Other
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, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = energy
Password file = energy.pwd

[DRIVE]
Theme = default
Comment = LST1 Drive ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, PLC Software and Configuration, Telescope Operations, Applications, Other, PLC + Control Software debugging, Tracking Debugging
Options Category = General, Hardware, Software, Other, Other_Debug, Issues
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, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = drive

[Startup checklist]
Comment = Shift startup checklist
Attributes = Author, D, M, Y, suic1, suic2, suic3, suic4, suic5, suwa1, suwc1, suwc2, suwc3, supa1, supc1, supc2, supc3, supc4, supc5, supc6, supc7, supc8, supc9, supc10
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = /usr/local/elog/html/startup_list.html
Custom edit form = /usr/local/elog/html/startup_list.html
Custom display form = /usr/local/elog/html/startup_list.html
List after submit = 1
Admin user = camera
Password file = camera.pwd

[Shutdown checklist]
Comment = Shift shutdown checklist
Attributes = Author, D, M, Y, sdsa1, sdtc1, sdtc2, sdtc3, sdtc4, sdtc5, sdtc6, sdtc7, sdtc8, sdtc9, sdtc10, sdtc11, sdtc12, sdtc13, sdtc14, sdfa1, sdfa2, sdfa3, sdfa4
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = /usr/local/elog/html/shutdown_list.html
Custom edit form = /usr/local/elog/html/shutdown_list.html
Custom display form = /usr/local/elog/html/shutdown_list.html
List after submit = 1
Admin user = camera
Password file = camera.pwd

[GENERAL ELOG PROPOSAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Category, System, Subsystem, Subject, Status
Options Type = Shift Summary, Report, Issue, Request, Announcements, Plans
Options Category = General, Observation, Safety, Maintenance, Intervention, Hardware, Software, Network, Other
Options System  = LST1{1}, Structure{2}, Camera{3}, Drive{4}, AMC{5}, IT{6}, Energy{7}
{1} MOptions Subsystem = Shift, Maintenance, Test
{2} MOptions Subsystem = Lower, Dish
{3} MOptions Subsystem = ECC, TIB, CACO, EVB, UCTS, Fibers, ClusCo, DATA, CACO/ClusCO, Calib box, Camera Server, Monitoring, Backplane, Observation, Daily calibration, Dragon, Operation, Trigger Mezzanine, PDB, CDTS, Switches, Cooling
{4} MOptions Subsystem = PLC, Telescope Operations, Applications, Control Software, Tracking
{5} MOptions Subsystem = CCD, AMC box, Pointing calibration
{6} MOptions Subsystem = Humidifier, Cooling
{7} MOptions Subsystem = UPS, Flywheel
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
Required Attributes = Author, Type, Category, System
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Category, System
Use Email Subject = $Type, $Subject
Email Type "Shift Summary" = mailing-list@cta-####.org
Email System Camera =  mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd
  69080   Wed Jan 22 16:10:51 2020 Question Daniel Pfuhldaniel.pfuhl@medizin.uni-leipzig.deRequestLinux | Windows | Mac OSX | All | Other3.1.4CSS for HTML Mails

Hi there,

we extensively use Logbuch as a change documentation platform.

E-Mail notifications for new entries are very important for us.

Since we store sensible data in our logbooks the server is protected by a firewall.

After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.

Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.

Any idea how to solved this issue?

Best regards,

daniel

  69081   Wed Jan 22 16:35:47 2020 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | Windows | Mac OSX | All | Other3.1.4Re: CSS for HTML Mails

The CSS has been embedded in the email end of 2018, so just upgrade your server.

https://bitbucket.org/ritt/elog/commits/5165daf35cc1fb066071827719079fe0c9aa5ffb

/Stefan

Daniel Pfuhl wrote:

Hi there,

we extensively use Logbuch as a change documentation platform.

E-Mail notifications for new entries are very important for us.

Since we store sensible data in our logbooks the server is protected by a firewall.

After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.

Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.

Any idea how to solved this issue?

Best regards,

daniel

 

ELOG V3.1.5-3fb85fa6