Logcheck devel - Oct 2004 - Bug#275946: newline not recognized when logcheck sends emails

Package: logcheck
Version: 1.2.27
Severity: normal

After creating a few local-* rules, Outlook now shows logcheck emails as
one long line. Reading the emails in a webmail client look fine though.

Note that this problem started after i created a few local-* rules. (as
far as i can tell)

Here is an example:

System Events
=-=-=-=-=-=-Oct 10 22:05:47 solara snmpd[7942]: Connection from 68.126.176.48
Oct 10
22:07:57 solara postfix/smtpd[14898]: lookup table has changed --
exiting Oct 10 22:10:49 solara snmpd[7942]: Connection from
68.126.176.48 Oct 10 22:15:48 solara snmpd[7942]: Connection from
68.126.176.48 Oct 10 22:20:47 solara snmpd[7942]: Connection from
68.126.176.48 Oct 10 22:25:15 solara pure-ftpd:
(?@adsl-68-126-239-39.dsl.pltn13.pacbell.net) [INFO] New connection from
adsl-68-126-239-39.dsl.pltn13.pacbell.net


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22
Locale: LANG=C, LC_CTYPE=C

Versions of packages logcheck depends on:
ii  adduser          3.51                    Add and remove users and groups
ii  cron             3.0pl1-81               management of regular background p
ii  debconf [debconf 1.3.20                  Debian configuration management sy
ii  debianutils      2.6.1                   Miscellaneous utilities specific t
ii  lockfile-progs   0.1.10                  Programs for locking and unlocking
ii  logcheck-databas 1.2.27                  A database of system log rules for
ii  logtail          1.2.27                  Print log file lines that have not
ii  mailx            1:8.1.2-0.20031014cvs-1 A simple mail user agent
ii  perl             5.8.3-3                 Larry Wall's Practical
Extraction
ii  postfix [mail-tr 2.0.18-1                A high-performance mail transport 
ii  sysklogd [system 1.4.1-10                System Logging Daemon

-- debconf information:
  logcheck/changes: 
* logcheck/install-note:

tags 275946 moreinfo
thanks

On Mon, 11 Oct 2004, Brendon Baumgartner wrote:
> After creating a few local-* rules, Outlook now shows logcheck emails as
> one long line. Reading the emails in a webmail client look fine though.
that's a pretty bad mail client AFAIK.
 
> Note that this problem started after i created a few local-* rules. (as
> far as i can tell)
anyway please send in all those local-* files,
so we may be able to reproduce.
 
--
maks

Processing commands for control at bugs.debian.org:
> tags 275946 moreinfo
Bug#275946: newline not recognized when logcheck sends emails
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

tags 275946 unreproducible
thanks

On Mon, 11 Oct 2004, Brendon Baumgartner wrote:
> After creating a few local-* rules, Outlook now shows logcheck emails as
> one long line. Reading the emails in a webmail client look fine though.
please pinpoint this problem which rule is creating trouble.
as i'm not able to reproduce this line-wrap problem,
i may have to close that bug.

anyways thanks for your bug report
a++ maks

Processing commands for control at bugs.debian.org:
> tags 275946 unreproducible
Bug#275946: newline not recognized when logcheck sends emails
Tags were: moreinfo
Tags added: unreproducible
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

On Fri, 22 Oct 2004, Brendon Baumgartner wrote:
> Started this discussion, might as well try and finish it. :)
thanks for feeback. :)
 
> Watch closely. The 2043 does NOT have the SLAPD rules and the 20:45 does.
> The report generated by the ladder has a linefeed problem. It seems to me
> that the slapd rules match a carriage return or line feed that the other
> rules do not. 
> 
> In summary:
> 2043 report: good. Even where slapd and kernel messages are mixed together.
> 2045 report: bad.
> 
> Let me know what you think.
> Brendon
> 
> (note, I only showed my additions. I removed all my rules that looked like
> they could match a line feed)
<snipp rules>

ok now we have something we can poke on even if looks wired
that removing more messages causes this line-wrap problem.

could you show as the output of
sed -e 's/[[:space:]]+$//' /var/log/syslog | egrep --text slapd | \
egrep --text -v '^\w{3} [ :0-9]{11} [._[:alnum:]-]+ slapd\[[0-9]+\]:'

as i have hands on an ldap server i'll may also try,
maybe a better idea comes up till then.

a++ maks

as nobody else gave input on that matter,
i'll try to dig further...

On Fri, 22 Oct 2004, Brendon Baumgartner wrote:
> Started this discussion, might as well try and finish it. :)
> 
> Watch closely. The 2043 does NOT have the SLAPD rules and the 20:45 does.
> The report generated by the ladder has a linefeed problem. It seems to me
> that the slapd rules match a carriage return or line feed that the other
> rules do not. 
> 
> In summary:
> 2043 report: good. Even where slapd and kernel messages are mixed together.
> 2045 report: bad.
> 
> Let me know what you think.
> Brendon
a possiblity would be to set "loglevel        0",
but i guess you have reasons not to do so. ;-)

what's your default locales?
is it an utf8, does a change to "oldstyle" iso help?
 
perhaps another to me unkown parameter changed your problem?

thanks for your feedback. :)

a++ maks