https://qa.mandriva.com/show_bug.cgi?id=26773 Summary : msec daily security report won't mail: Invalid or incomplete multibyte or wide character
Product : Mandriva Linux
Component : Core Packages
Version : Cooker
RPM Package: msec
Keywords : Triaged
Status : ASSIGNED
Severity : major
Priority : high
Assigned To:
thauvin@...
Reported By:
ftg@...
steletch@... changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |36848
--- Comment #21 from
steletch@... 2008-12-02 17:22:57 CEST ---
I'll test on my own 2009.0 box and if it fixes the problem, i'll issue an
update for those (this is a long standing bug and if the above fixes the issue,
that'd be cool).
Morevoer, i wonder why Andreas limited the substitution in sed, i do not see
why only the first characters. Morevoer this command [^[:print:]] seems defined
in ascii and iso8859-1 but i don't know how it works in UTF8...
I suspect what Andreas what effectively wanting to use is ctrnl but not print.
Stef
----------------------------------------------------------------------------
Original Bug Text:
On one particular up-to-date cooker system, I get the following output from the
nightly /etc/cron.daily run:
Invalid or incomplete multibyte or wide character
. . . message not sent.
"//dead.letter" 2353/238304
The /dead.letter file is the msec "Security Violations" report, 2353 is the
number of lines in the file, and 238304 is the number of bytes in the file
(including the closing \n).
The system was installed with multiple languages: English (3 varieties), French,
German, Italian, and Spanish; however, US English is the activated language, and
none of the others had been activated or switched to prior to this happening.
Other current cooker systems with the same language choices don't exhibit this
behavior.
I'll attach the dead.letter file. Since the complain mentions the end of the
file, I assume that some piece of data (message or filename) unique to this
system is tripping the test for a multibyte character. There may or may not be
an invalid or open-ended multibyte sequence in the data, but if that can validly
occur, then msec should probably be mailing the report as an attachment rather
than text/plain, which I assume is the root of the problem.
--
Configure bugmail:
https://qa.mandriva.com/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the QA contact for the bug.
