Hi all, I've got this error in system log - what is it? ---- Tue Oct 7 07:36:16 2003 notice OTRS-PM-10 New Ticket [108484] created (TicketID=8744, ArticleID=17556). Tue Oct 7 07:36:16 2003 error OTRS-PM-10 Need Content! ---- Regards, Alex
On Tuesday, October 07, 2003 8:48 AM
Alex Mihicinac
I've got this error in system log - what is it?
---- Tue Oct 7 07:36:16 2003 notice OTRS-PM-10 New Ticket [108484] created (TicketID=8744, ArticleID=17556). Tue Oct 7 07:36:16 2003 error OTRS-PM-10 Need Content! ----
Which version of OTRS is running on which system? Robert Kehl
---- Tue Oct 7 07:36:16 2003 notice OTRS-PM-10 New Ticket [108484] created (TicketID=8744, ArticleID=17556). Tue Oct 7 07:36:16 2003 error OTRS-PM-10 Need Content! ----
Which version of OTRS is running on which system?
OTRS 1.1.3 on sunos 5.8 (i saw this error on earlier versions of OTRS too and never knew what it was about) Regards, Alex
On Friday, October 10, 2003 4:41 PM
Alex Mihicinac
---- Tue Oct 7 07:36:16 2003 notice OTRS-PM-10 New Ticket [108484] created (TicketID=8744, ArticleID=17556). Tue Oct 7 07:36:16 2003 error OTRS-PM-10 Need Content! ----
Which version of OTRS is running on which system?
OTRS 1.1.3 on sunos 5.8 (i saw this error on earlier versions of OTRS too and never knew what it was about)
Can you give a bit more detail on how to produce this error, if reproducable at all? Can you switch on debugging to show more logging details? Do your additional logs say anything - esp. Apache's? Regards, Robert Kehl
Hi,
Can you give a bit more detail on how to produce this error, if reproducable at all?
Tell how to get them :) I haven't figured out why it's showing this error. :-/
Can you switch on debugging to show more logging details?
How can I do that?
Do your additional logs say anything - esp. Apache's?
Nope, nothing else in logs. Regards, Alex
On Mon, Oct 13, 2003 at 09:29:29AM +0200, Alex Mihicinac wrote:
Can you give a bit more detail on how to produce this error, if reproducable at all?
Tell how to get them :) I haven't figured out why it's showing this error. :-/
Today I got the same error. It was a spam email with no body (not one character). :-/
Alex
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "Security is a process, not a product." - Bruce Schneier
On Monday, October 13, 2003 9:29 AM
Alex Mihicinac
Hi,
Can you give a bit more detail on how to produce this error, if reproducable at all?
Tell how to get them :) I haven't figured out why it's showing this error. :-/
You could feed the offending eMail again and again and see if it breaks everytime. As Martin says, he got this error with a completely empty mail. Is the body of your mail empty, too?
Can you switch on debugging to show more logging details? How can I do that?
in Config.pm: # 0=off; 1=log if there exists no entry; 2=log all; $Self->{Debug} = 0;
Do your additional logs say anything - esp. Apache's? Nope, nothing else in logs.
hth, Robert
Hi,
Can you give a bit more detail on how to produce this error, if reproducable at all?
Tell how to get them :) I haven't figured out why it's showing this error. :-/
You could feed the offending eMail again and again and see if it breaks everytime.
As Martin says, he got this error with a completely empty mail. Is the body of your mail empty, too?
Can you switch on debugging to show more logging details? How can I do that?
in Config.pm:
# 0=off; 1=log if there exists no entry; 2=log all; $Self->{Debug} = 0;
Hmm.. It's true. This happens when mail with empty body arrives. But is this an error? Sometimes there is only short comment in Subject and no body message. I like to have my logs error free as much as it's possible, so i suggest to remove this error warning. Why it was made in first place? Best regards, Alex
On Wednesday, October 15, 2003 11:07 AM
Alex Mihicinac
As Martin says, he got this error with a completely empty mail. Is the body of your mail empty, too?
Hmm.. It's true. This happens when mail with empty body arrives. But is this an error? Sometimes there is only short comment in Subject and no body message. I like to have my logs error free as much as it's possible, so i suggest to remove this error warning. Why it was made in first place?
OTRS is a System for managing communication (in general). Although you might think of communicating to each other via the subject line, being restricted to its limitations, most people prefer to have s.th. like they had when using a white sheet of paper and a pencil instead of email. Ie. The body of an email is there for holding the *content*, the subject should only give a clue about it. Regards, Robert Kehl
OTRS is a System for managing communication (in general). Although you might think of communicating to each other via the subject line, being restricted to its limitations, most people prefer to have s.th. like they had when using a white sheet of paper and a pencil instead of email. Ie. The body of an email is there for holding the *content*, the subject should only give a clue about it.
I agree. But people do that. What I was suggesting is - for example - rename "error - Need Content" to "warning - Need Content". Best regards, Alex
participants (3)
-
Alex Mihicinac -
Martin Edenhofer -
Robert Kehl