Logcheck devel - Jan 2006 - Bug#344832: (fwd) Re: Bug#344832: correct subject header

----- Forwarded message from General Stone <generalstone at gmx.net> -----

X-Original-To: maks at sternwelten.at
Date: Mon, 2 Jan 2006 14:59:03 +0100
From: General Stone <generalstone at gmx.net>
To: maximilian attems <maks at sternwelten.at>
Subject: Re: [Logcheck-devel] Bug#344832: correct subject header

On Mon, Jan 02, 2006 at 02:09:48PM +0100, maximilian attems
wrote:
> please provide the noncorrect subject line and what is your wish?
> 
> reading the switches it seems pretty clear that the highest alerts wins
> as expeceted.
 
If I became an email with the content:
--------------------------------------
Security Events for su
=-=-=-=-=-=-=-=-=-=-=-
.
.
.

System Events
=-=-=-=-=-=-.
.
.

The subject line is: 
--------------------
"Subject: [logcheck] t-39-6-gs 02-01-2006 14:30 Security Events"

And I wish to change it to:
---------------------------
"Subject: [logcheck] t-39-6-gs 02-01-2006 14:30 Security Events, System
Events"

So that anybody can filter and split the mail like priority.
> > +# Modified by Markus Nass <generalstone at gmx.net>
> > +
> >  # This file is part of Logcheck
> 
> a bit bold for a 4 line patch.
I include this line automaticly, because I can see that this is not the
original from the packet but important for me not to override at an
update.

-Markus Nass

-- 
Key fingerprint = DC3C 257C 2B71 8FA4 F609  F7F7 7C14 F806 5665 77FD

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Was nicht fliegen kann, kann auch nicht abst?rzen.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



----- End forwarded message -----
-- 
maks

On 3 Jan 2006, at 01:18, maximilian attems wrote:
> ----- Forwarded message from General Stone <generalstone at gmx.net>
> -----
> From: General Stone <generalstone at gmx.net>
> To: maximilian attems <maks at sternwelten.at>
> Subject: Re: [Logcheck-devel] Bug#344832: correct subject header
>
> On Mon, Jan 02, 2006 at 02:09:48PM +0100, maximilian attems wrote:
>> please provide the noncorrect subject line and what is your wish?
>>
>> reading the switches it seems pretty clear that the highest alerts  
>> wins
>> as expeceted.
<snip>
> The subject line is:
> --------------------
> "Subject: [logcheck] t-39-6-gs 02-01-2006 14:30 Security Events"
>
> And I wish to change it to:
> ---------------------------
> "Subject: [logcheck] t-39-6-gs 02-01-2006 14:30 Security Events,  
> System Events"
>
> So that anybody can filter and split the mail like priority.
If there are Security Events and System Events then the subject will  
include Security Events, if there are only System Events, the subject  
will be System Events. I don't see how making the subject more  
complicated will enhance filtering - users can already filter on  
Security Events.

-- 
-Jamie L. Penman-Smithson <jamie at silverdream.org>
  t: +44 1273 424795; f: +44 1273 424795
  PGP: C0A7 955E EED6 A309 23D7 863B C76A 26A3 F0DC FCA8
  never send mail to: oubliette.z at gmail.com


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url :
http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20060212/7fbc405a/attachment.pgp