Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 372 of 808  Not logged in ELOG logo
icon5.gif   Entry size too large for email notification, posted by Jacky Li on Tue May 19 12:26:39 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.

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

Jacky

icon5.gif   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.

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

Jacky

    icon2.gif   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
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

    icon2.gif   Re: Entry size too large for email notification, posted by Stefan Ritt on Fri May 22 13:43:14 2015 

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

 

icon5.gif   Fixed text, posted by Neal Grafton on Tue May 26 10:38:36 2015 

I'd like to fix text or table in the subject field that can't be deleted or moved. 

Can that be done in config? Example - 

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

    icon2.gif   Re: Fixed text, posted by Andreas Luedeke on Tue May 26 11:26:12 2015 
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.

Cheers, Andreas

Neal Grafton wrote:

I'd like to fix text or table in the subject field that can't be deleted or moved. 

Can that be done in config? Example - 

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

 

    icon2.gif   Re: Fixed text, posted by Neal Grafton on Tue May 26 12:34:44 2015 

Sorry I call this field that you write in the subject field, a little confusing.

So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)

Neal

Andreas Luedeke wrote:
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.

Cheers, Andreas

Neal Grafton wrote:

I'd like to fix text or table in the subject field that can't be deleted or moved. 

Can that be done in config? Example - 

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

 

 

    icon2.gif   Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Kamen Nikolov on Tue May 26 22:03:05 2015 

Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?

Thanks,

Kamen

Kamen Nikolov wrote:

Hello,

I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?

Additional info:

I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).

Please let me know if I am doing something incorrectly?

Thanks

 

ELOG V3.1.5-3fb85fa6