Re: Logwatch Dovecot Deliver Summary
Patrick Vande Walle <[email protected]>
| Newsgroups | gmane.comp.log.logwatch.devel |
|---|---|
| Organization | ISOC Luxembourg ASBL |
| Message-ID | <[email protected]> |
Dennis,
Please try the following patch:
--- dovecot.orig 2014-05-10 09:45:39.795499290 +0200
+++ dovecot 2014-05-10 10:01:25.538429031 +0200
@@ -179,7 +179,7 @@
}
# 'lda' for dovecot 2.0, 'deliver' for earlier versions
- } elsif ( ($User, $Mailbox) = ( $ThisLine =~ /^$dovecottag
(?:lda|deliver)\((.*)\): msgid=.*: saved mail to (\S+)/ ) ) {
+ } elsif ( ($User, $Mailbox) = ( $ThisLine =~ /^$dovecottag
(?:lda|deliver)\((.*)\):( Info:)? msgid=.*: saved mail to (\S+)/ ) ) {
$Deliver{$User}{$Mailbox}++;
# For Sieve-based delivery
This is untested. My system uses the Sieve lda, which returns other
strings.
If it works for you, please report back so Mike can update the sources.
Regards,
Patrick Vande Walle
On 09/05/14 18:07, Klaipedaville on Google wrote:
> Hello Mike,
>
> OK. Thank you very much for replying so quickly. I will try to tweak
> it for some more time but I am really at loss. I have been
> experimented and testing all the possible and impossible things for 3
> days now but have never managed it up to now. I even started writing a
> new perl script (just building on your dovecot script at the end) but
> I am not that good at perl (much better at php) and still cannot
> figure out where are all the variables declared and where do they all
> come from in there. I tried to add some simple testers for lda parts
> in your dovecot script just to see which lines fail but they have
> never worked and it looks like that a lot of things are simply
> irresponsive in there that is the code simply does not respond... Is
> there actually a match that fails or there is just nothing that would
> manage lda for dovecot 2.1.7? The only line I can see is “# 'lda' for
> dovecot 2.0, 'deliver' for earlier versions”. Does it mean that
> perhaps my dovecot 2.1.7 is not supported at all? Which exact “earlier
> versions” are those?
>
> If I add these to my ignore.conf then my report for dovecot service is
> going to be totally empty because this is all that I receive from it
> at the moment.
>
> Were you aware of this issue? I’ve also tried to check it with Debian
> but after a lively correspondence for a couple of days and after all
> my detailed reports with very detailed specifications what I modified
> and checked they disappeared, most probably re-producing and testing
> it at their side. I still look forward to receiving their reply about it.
>
> I really do appreciate your suggestions. Would be also thankful for
> any further comments / advices you may additionally have.
>
> Regards,
> Dennis.
>
>
> *From:* Mike Tremaine <mailto:[email protected]>
> *Sent:* Friday, May 9, 2014 18:29
> *To:* Klaipedaville on Google <mailto:[email protected]>
> *Cc:* [email protected]
> <mailto:[email protected]> ; [email protected]
> <mailto:[email protected]> ; [email protected] <mailto:[email protected]>
> *Subject:* Re: [Logwatch-devel] Logwatch Dovecot Deliver Summary
>
>
> Thank you.. yes you are up to date and this is featuer that will have
> to be added.
>
> The short term solution might be to add
>
>> lda(mail <mailto:[email protected]>@mydomain.
>> <mailto:mail@mydomain.>com): Info: msgid
>
> to your ignore.conf file that will keep the 50000 lines from hitting
> your report. But long term someone has to figure out why the match is
> failing and fix it.
>
> -Mike
>
>
> On May 9, 2014, at 8:25 AM, Klaipedaville on Google wrote:
>
>> Hello,
>>
>> Thank you so much for replying.
>>
>> Well, the version as per your link says this:
>> ########################################################
>> # $Id: dovecot 159 2013-08-19 09:35:30Z stefjakobs $
>> ########################################################
>>
>> The version that I have says the same:
>> ########################################################
>> # $Id: dovecot 159 2013-08-19 09:35:30Z stefjakobs $
>> ########################################################
>>
>> Are these the right lines where the version is advised? Would really
>> appreciate any more suggestions / help. Many thanks!
>>
>> Regards,
>> Dennis.
>> *From:* Mike Tremaine <mailto:[email protected]>
>> *Sent:* Friday, May 9, 2014 17:13
>> *To:* Klaipedaville on Google <mailto:[email protected]>
>> *Cc:* [email protected]
>> <mailto:[email protected]> ; [email protected]
>> <mailto:[email protected]> ; [email protected] <mailto:[email protected]>
>> *Subject:* Re: [Logwatch-devel] Logwatch Dovecot Deliver Summary
>>
>>
>>
>> Check and see if the SVN version of the dovecot script is newer then
>> yours
>>
>> _http://sourceforge.net/p/logwatch/code/HEAD/tree/scripts/services/dovecot_
>>
>> On May 8, 2014, at 9:36 PM, Klaipedaville on Google wrote:
>>
>>> Hello there,
>>>
>>> I was wondering and would be really grateful if you could please,
>>> advise on the following.
>>>
>>> Logwatch 7.4.0 (released 11/08/13) in combination with Dovecot 2.1.7
>>> installed on Debian Wheezy.
>>>
>>> I have Logwatch reporting dovecot service with each connection /
>>> saved mail per line as shown below. Now each line represents a
>>> separate connection as far as I understand and if I have for example
>>> 50 000 connections per day I get 50 000 lines in my daily Dovecot
>>> report. This is all that I receive for Dovecot, no summaries, never.
>>>
>>> --------------------- Dovecot Begin ------------------------
>>>
>>> **Unmatched Entries**
>>> lda(mail <mailto:[email protected]>@mydomain.
>>> <mailto:mail@mydomain.>com): Info:
>>> [email protected]
>>> <mailto:[email protected]>: saved mail to
>>> INBOX: 1 Time(s)
>>> lda(mail <mailto:[email protected]>@mydomain.com
>>> <mailto:[email protected]>): Info:
>>> [email protected]
>>> <mailto:[email protected]>: saved mail to
>>> INBOX: 1 Time(s)
>>> lda(mail <mailto:[email protected]>@mydomain.com
>>> <mailto:[email protected]>): Info:
>>> [email protected]
>>> <mailto:[email protected]>: saved mail to
>>> INBOX: 1 Time(s)
>>> lda(mail <mailto:[email protected]>@mydomain.com
>>> <mailto:[email protected]>): Info:
>>> [email protected]
>>> <mailto:[email protected]>: saved mail to
>>> INBOX: 1 Time(s)
>>>
>>> ---------------------- Dovecot End -------------------------
>>> Is it possible to set it to receive summaries only as per example
>>> below? The matter is that summaries never arrive at all.
>>>
>>>
>>> if ( ( $Detail >= 5 ) and (keys %Connection)) {
>>> print "\n[Dovecot IMAP and POP3] Connections:".
>>> "\n====================================".
>>> "\nPOP3 IMAP Total Host".
>>> "\n" . "-" x 72;
>>>
>>> [Dovecot IMAP and POP3] Connections:
>>> ====================================
>>> Host | POP3 | IMAP | Total
>>> -------------------------------------- | --------- |--------- |
>>> ---------
>>> 1.1.1.1 | 10 | 0 | 10
>>> 2.2.2.2 | 518 | 0 | 518
>>> -------------------------------------------------------------------------
>>> 528 | 0
>>> | 528
>>> User one: (199 POP3)
>>> From 1.1.1.1: 174 Time(s)
>>> From 2.2.2.2: 25 Time(s)
>>> Total: 199 Time(s)
>>>
>>> User two: (199 POP3)
>>> From 1.1.1.1: 174 Time(s)
>>> From 2.2.2.2: 25 Time(s)
>>> Total: 199 Time(s)
>>>
>>> and so on...
>>>
>>> I thank you for your time and look forward to hearing from you soon.
>>> Many thanks in advance!
>>>
>>> Regards,
>>> Dennis.
>>>
>>> ------------------------------------------------------------------------------
>>> Is your legacy SCM system holding you back? Join Perforce May 7 to
>>> find out:
>>> • 3 signs your SCM is hindering your productivity
>>> • Requirements for releasing software faster
>>> • Expert tips and advice for migrating your SCM now
>>> http://p.sf.net/sfu/perforce_______________________________________________
>>> Logwatch-devel mailing list
>>> [email protected]
>>> <mailto:[email protected]>
>>> https://lists.sourceforge.net/lists/listinfo/logwatch-devel
>>
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Logwatch-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/logwatch-devel