Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 525 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6460 Entries 
Goto page Previous  1, 2, 3 ... 524, 525, 526 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  67397   Tue Dec 11 10:17:11 2012 Reply Ron Beekmanron.beekman@gmail.comBug reportWindows2.7.5-2130Re: Error 554 MailTransferAgentServer ESMTP not accepting messages

Stefan Ritt wrote:

Ron Beekman wrote:

Hello,

We use ELOG for many years and enjoy it's functions every day!

Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages

We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.

We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.

We had this error in the past and found out that the cause of this error lies in (network) time-outs.

Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?

Any replies are highly appreciated!

T I A !
 

Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log? 

Hello Stefan,

Thanks you for entering this thread !

Fortunately, we were able to solve the problem. A reboot of the DNS server used by the MTA (Mail Transfer Agent Server) to check the from and to address did the trick.

This server now responds within the timeout period in ELOG.

It still would be handy if you could add a parameter to the config file that allows us to fiddle with the timeout value. The DNS server used by the MTA has to deal with heavy load.

Best regards,
Ron

 

 

 

 

  69837   Wed Sep 25 16:00:06 2024 Reply Nick Sauerweinnick.sauerwein@luxtelligence.aiBug reportLinux | Windows | Mac OSXELOG V3.1.5Re: Equation Editor does not work

We have observed the same issue. Did the CodeCogs api change? 

Thanks for the help.

Dominic wrote:

Hi!

I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log? 

Thank you!

 

  69839   Tue Nov 5 15:51:26 2024 Reply Dominicdominic@nowhere.coBug reportLinux | Windows | Mac OSXELOG V3.1.5Re: Equation Editor does not work

is there any update on this bug? Has anyone else observed the same problem?

Dominic wrote:

Hi!

I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log? 

Thank you!

 

  69860   Mon Jan 6 14:59:06 2025 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux | Windows | Mac OSXELOG V3.1.5Re: Equation Editor does not work

Apparently Codecogs have changed their URL. I tried the update from 

  https://editor.codecogs.com/depr/CK_Editor_v4x.php

but it did not help. The CK Editor v5 is quite different from v4 (like they require node.js to install it), so putting it into elog would be some major work. 

Stefan

Dominic wrote:

is there any update on this bug? Has anyone else observed the same problem?

Dominic wrote:

Hi!

I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type latex formula in the log? 

Thank you!

 

 

  67914   Tue May 19 16:34:20 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification
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
Jacky Li wrote:

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.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky
  67929   Fri May 22 13:43:14 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification

The size is defined by the variable MAX_CONTENT_LENGTH in elogd.c which is set to 10 MB. But email attachments are encoded in ASCII form, so they take useually 3-4 times the space of the binary format. If you have problems with large emails, you can use the option "Email Format = 111" which causes only the names of attachments to be included in email notifications. Users can then still click on the elog link inside the email notification and download the attachment from the elog page.

Jacky Li wrote:

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.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

  68829   Fri Jul 13 19:14:21 2018 Reply Lars Martinlmartin@triumf.caQuestionLinux2.9.2Re: Entry size too large for email notification

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 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
Jacky Li wrote:

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.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

  68837   Mon Aug 27 13:07:28 2018 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Entry size too large for email notification

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.

Stefan

Lars Martin wrote:

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 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
Jacky Li wrote:

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.

May I know what is the limit of the entry size and how do I change it?  Thank you.

Jacky

 

 

Goto page Previous  1, 2, 3 ... 524, 525, 526 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6