Re: Can the elog client submit an entry with a html body?, posted by Stefan Ritt on Tue Nov 2 17:47:43 2004
|
> Is it possible to submit an entry with a html body using the elog client?
I added a "-H" flag for that. New version of elog.c under CVS and in the next
release. |
|
Re: Can the elog client submit an entry with a html body?, posted by Kristinn B. Gylfason on Tue Nov 2 18:15:09 2004
|
> > Is it possible to submit an entry with a html body using the elog client?
>
> I added a "-H" flag for that. New version of elog.c under CVS and in the next
> release.
Great! Thanks.
Kristinn |
Trying to remove "mailto:" from the email address, posted by Matt Kimball on Wed Oct 12 23:59:13 2005 
|
We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file.
Thanks
Matt |
|
Re: Trying to remove "mailto:" from the email address, posted by Stefan Ritt on Thu Oct 13 08:32:20 2005
|
| Matt Kimball wrote: | | We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file. |
The "mailto:" is there for good reason. After you submit the entry, elogd converts the "mailto:" into
<a href="mailto:user@domain.com">user@domain.com</a>
so the browser shows the email address as a link. If you click it, the browser automatically opens your email client with the email address already in the "To:" field. The same works in the main text body. So if I put "mailto:stefan.ritt@psi.ch", it gets converted automatially to "stefan.ritt@psi.ch", a feature many people rely on.
Now from your request it looks to me like you want email notifications, so you put
Email System CareWare = ..., $user_email
In that case the "mailto:" gets automatically stripped during the email notification, so the user_email gets entered and will be used correctly for the notification. |
|
Always suppress email notifications, posted by Bartjan Wattel on Wed Jul 14 13:31:33 2004
|
Hi - again a configuration question.
How can I suppress all email notifications? The "Suppress default = 2" flag
allows me to always produce a notification, but the flag does not provide
an option to never produce a notification. The flag "Suppress Email on
edit" does help a bit, but still notifications for new messages will be
sent.
I'm looking forward to your fast response... So far your support is
fantastic!
Bartjan Wattel |
Request: limit size of attachments, posted by Bartjan Wattel on Wed Jul 14 13:58:26 2004
|
hi again,
we have been doing a bit of stress testing for Elog. The most important
thing we found is that Elog stops responding when a user uploads a large
attachment (we used a 240 Mb attachment).
Is it possible to add a flag in the configuration file, to specify the
maximum size of an attachment?
Bartjan Wattel |
|
Re: Always suppress email notifications, posted by Stefan Ritt on Wed Jul 14 16:11:46 2004
|
> How can I suppress all email notifications? The "Suppress default = 2" flag
> allows me to always produce a notification, but the flag does not provide
> an option to never produce a notification. The flag "Suppress Email on
> edit" does help a bit, but still notifications for new messages will be
> sent.
Suppress email to users = 1
RTFM |
|
Re: Request: limit size of attachments, posted by Stefan Ritt on Thu Jul 15 22:01:55 2004
|
> Is it possible to add a flag in the configuration file, to specify the
> maximum size of an attachment?
I implemented a "max content length = xxx" flag, which defaults to 10MB. If an
attachment is larger, an error gets displayed. The problem is that elogd can
only send the error message to the browser *after* it received the whole
request, so it has to "drain" the 240 MB first, which could take quite some
time on a slow connection.
Alternatively, I can cut the connection to the browser immediately, since the
HTTP header contains the content length after the first ~500 bytes, but in
that case the browser only shows a message box "Document contains no data"
which gives the user noe clue of what's wrong.
Anyhow the biggest problem of elog in high stress environments is that it's
single threaded. So if someone issues a search in a large logbook, it could
take some time, in which elog cannot respond to other requests. Maybe I will
find time in the future to make elog multithreaded, but certainly not in the
near future. |