Description of problem:

When a log file processed by logwatch contains lines terminated with <CR><LF>,
<CR> is treated as a regular character rather than a part of the line break.
This has two unpleasant consequences:

(1) The log message may no longer match the specified pattern, making the line
    an unmatched entry. This may or may not be the expected behaviour.

(2) When printing a <CR><LF>-terminated entry, be it matched or unmatched, the
    carriage return is interpreted literally which breaks the output
    formatting.

Consider the following example, paying special attention to the **Unmatched
Entries** section in logwatch output:

# file /var/log/maillog
/var/log/maillog: ASCII text, with CRLF line terminators

# cat /var/log/maillog
Sep 24 04:17:27 mail1 sm-mta[14263]: k808NQxv028473: <wyman>... User unknown
Sep 24 04:19:01 mail1 sm-mta[12654]: k8O8F027026507: <cotter>... User unknown
Sep 24 04:25:33 mail1 sm-mta[14462]: k8O8VWJc037652: <helman>... User unknown

# logwatch --print --service sendmail --range all

 ################### Logwatch 7.3.6 (05/19/07) ####################
        Processing Initiated: Mon Jan  4 10:29:17 2016
        Date Range Processed: all
      Detail Level of Output: 0
              Type of Output: unformatted
           Logfiles for Host: qeos-32.lab.eng.rdu2.redhat.com
  ##################################################################

 --------------------- sendmail Begin (detail=3) ------------------------

 **Unmatched Entries**
: 1 Time(s)@tallhart.com>... User unknown
: 1 Time(s)manderly.com>... User unknown
: 1 Time(s) pyke.com>... User unknown
 ---------------------- sendmail End -------------------------


 ###################### Logwatch End #########################


Version-Release number of selected component (if applicable):
logwatch-7.3.6-52.el6.noarch