Need to change port 25, posted by Yanick Vachon on Mon Nov 26 17:32:31 2018
|
Hi,
We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?
Thanks |
Re: Need to change port 25, posted by Andreas Luedeke on Tue Nov 27 08:19:11 2018
|
This is nicely explained in the documentation: https://elog.psi.ch/elog/config.html#global
The following options are specific to the [global]
section:
Port = <port> |
|
Re: Need to change port 25, posted by Stefan Ritt on Tue Nov 27 08:59:45 2018
|
I believe Yanick means the SMTP port, not the port under which elogd is listening. The SMPT port is hard wired to 25, because port 587 was not yet defiend
when I wrote that code. I can make this a variable, but only if it works. So Yanick can you test if port 587 accepts normal SMTP commands? We don't
have such a new server at our lab and I cannot test it. Under Windows you can open a command prompt and telnet to the mail server: |
Re: Need to change port 25, posted by Yanick Vachon on Tue Nov 27 15:21:31 2018 
|
I Stefan, it works with the 587 port.
|
|
Re: Need to change port 25, posted by Stefan Ritt on Wed Nov 28 16:24:43 2018
|
Ok, so I added the option
STMP port = xxx
where you can specify 587 to override the default port 25. I committed the changes to bitbucket. Can you compile from sources, or do I have to |
|
Re: Need to change port 25, posted by Yanick Vachon on Wed Nov 28 18:23:59 2018
|
Good!
so, i've tried to compile but iwonder if i does it correctly,
look at the error i got: |
|
Re: Need to change port 25, posted by Stefan Ritt on Thu Nov 29 09:56:45 2018
|
I put a new executable for you under https://elog.psi.ch/elog/download/windows/
It's named elog314-2.exe
Best, |
|
Re: Need to change port 25, posted by Yanick Vachon on Wed Nov 28 16:43:14 2018
|
Hello,
now we kwow it's working are you gonne send us a version with the SMTP port editable?
Thanks! |
|
Re: Need to change port 25, posted by Stefan Ritt on Wed Nov 28 16:53:58 2018
|
Just read my post 20 mins ago!
Stefan
Yanick |
|
messy code for chinese charactor, posted by Wenhao Huang on Fri Oct 26 08:56:59 2018
|
| The Chinese character appears messy code. The encoding way is the default utf-8. How can I solve this problem? |
|
Re: messy code for chinese charactor, posted by Stefan Ritt on Sat Oct 27 10:51:12 2018
|
Can you post a screenshot?
[quote="Wenhao Huang"]The Chinese character appears messy code. The encoding way is the default utf-8. How can I solve this problem?[/quote] |
How many "Extendable options" can I add?, posted by Devrim Esenturk on Fri Oct 26 14:22:59 2018
|
Hi
I am trying to add "Extendable options" for some attribute as below example. However button to add new item for list appears only for
the first "Extendable options", if disable the first with (;), button appears for the second. It means elog add new item button only the first |
Re: How many "Extendable options" can I add?, posted by Grant Jeffcote on Fri Oct 26 16:46:52 2018
|
David,
Try
Extendable options = Require Model, Require Lens, Require Other, |
|
Re: How many "Extendable options" can I add?, posted by Grant Jeffcote on Fri Oct 26 16:50:48 2018
|
Apologies that should have been Devrim (autocorrect again) :-(
Grant
Jeffcote wrote:
David, |
|
Re: How many "Extendable options" can I add?, posted by Devrim Esenturk on Fri Oct 26 19:15:19 2018
|
No problem :)
Your suggestion worked as it must be. I didn't see "Extendable options = <list>" on guide :/
I guess I need rest a little bit... :( |
|
Buttons missing in ckeditor, posted by Roland Beyer on Thu Oct 11 10:51:17 2018
|
Hello everybody,
we had to setup a new server for our elog some time ago because the old one crashed. We are now running version ELOG V3.1.1-0767eb0.
In the previous installation we had these nice buttons for file upload, time stamp and equation editor, which are also available here in the |
|
Re: Buttons missing in ckeditor, posted by Stefan Ritt on Fri Oct 12 10:17:20 2018
|
Have you selected "HTML" encoding (below the main message box). The HTML editor is not activated if you have "plain" text encoding.
Did you try the default elogd.cfg file? If you modified the config file and did a mistake there, the program can for example not properly find all directories.
Also makse sure you did a full install with "make install", not just update the executable. |
|
Re: Buttons missing in ckeditor, posted by Roland Beyer on Fri Oct 12 11:56:26 2018
|
Dear Stefan,
thanks for your hints. Meanwhile we already solved the problem. I think it was caused by the recovery from a backup version after the server
crash ... and the retirement of the person who did the previous installation. |
|
Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Tue Sep 11 19:46:40 2018
|
Tried compiling on FC27 and 28, both result in binaries but with serious issues; writing data larger than then allowed.
Example output:
make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations |
|
Re: Compile issues on Fedora withe current elog source, posted by Stefan Ritt on Wed Sep 12 11:10:18 2018
|
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(),
which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please
post the full warning list here. |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:25:07 2018
|
I would like to try the new code, I don't see it on elog/download/tar/.
Do you keep updates elsewhere like on get or sourceforge?
Stefan |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:57:31 2018
|
A quick test suggests I can't just replace sprintf with snprintf.
Original error:
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256 [-Wformat-overflow=] |
|
Re: Compile issues on Fedora withe current elog source, posted by Andreas Luedeke on Wed Sep 12 20:52:22 2018
|
Stefan said "code is commited": that means you can download the latest version from https://bitbucket.org/ritt/elog, as described in https://elog.psi.ch/elog/download.html,
and then compile it. Clear now?
Stefan |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Thu Sep 13 06:12:59 2018
|
Latest compile effort on Fedora 28 using the bitbucket source downloaded at 21:12 PDT:
make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -c -o mxml.o mxml/mxml.c |
|
Entry size too large for email notification, posted by Jacky Li on Tue May 19 12:27:01 2015
|
Hi,
I am doing an inline image that is about 2.2 MB. When I do a submit, I got the following message:
Error sending Email via <i>"<email server>"</i>: Entry size too large for email notification. |
|
Re: Entry size too large for email notification, posted by Andreas Luedeke on Tue May 19 16:34:20 2015
|
Hi Jacky,
if I read the source code correctly then the maximum size of a base64 encoded email is hard coded to be 10 MB in elogd.h (recompile
after changing it):
#define MAX_CONTENT_LENGTH 10*1024*1024
But
I think that an 2.2 MB image should easily fit into that.
Andreas
|
|
Re: Entry size too large for email notification, posted by Lars Martin on Fri Jul 13 19:14:21 2018
|
Wouldn't it make sense for ELog (by default) to still notify, but not send the attachments by e-mail if the size limit is reached?
Andreas
Luedeke wrote:
Hi Jacky,
if I read the source code correctly |
|
Re: Entry size too large for email notification, posted by Stefan Ritt on Mon Aug 27 13:07:28 2018
|
That's how it is implemented. If you use
Max email attachment size = 1000000
then attachments below 1 MB are sent as attachments, and if the attachment is above 1 MB, then only a link to the attachment in the elog is sent. |
|
Changing of entries after expired time restriction by synchronisation, posted by Gino Guenzburger on Thu Aug 16 13:33:39 2018
|
I'm working on setting up an elog as lab-journal in our group with the following set-up:
The elog is running on a server, with no back-end access for the users.
Multiple people will use it, all loging in with the
same user-name and password.
The entries submitted to the log-book can only be edited for 24hours, as defined by the "Restrict edit time= |
|
Problem with eloglang.german_UTF8, posted by Andreas Luedeke on Tue Aug 7 10:53:45 2018
|
I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make
the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes |