See the thread about "Incoming email suddenly dead" for previous
posting. And http://www.mail-archive.com/[email protected]/msg06645.html.
Elsewhere I did see someone speculate/point out that the problem could
be with Message-Ids containing the percent sign(%) being passed to the
sprintf in Syslog.pm. From my own experience, I'd say that this rings
true. It was a message that suddenly broke the queue and it's
message-id did contain the '%' character.
If this is all true, then this seems to represent a potentially serious
problem for OTRS installations. In same astute thread that speculated
about the cause of this error, they did mention the potential for DOS
attacks against OTRS systems with such a message-id. From what I can
find, having this character in the id does not seem out of line with the
specification -- however, I am not even close to authoritative on the
subject.
OTRS community -- please set me straight. If my understanding is in
error here, and my particular installation lacks some sort of previous
patch/fix for this problem, please let me know. What is your
assessment? I'm sorry that I can't find and cite the URL source of the
original speculation that led to my own confirmed solution and source of
the problem.
--
jt
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support orr consulting for your OTRS system?
=> http://www.otrs.com/
