☩ Walking in Light with Christ – Faith, Computing, Diary

No Responses to “…”

1. Thibs says:

   August 5, 2010 at 12:25 am

   Firefox 3.6.8 Ubuntu 10.04 x64
   Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8

   If you’re agree, I’ll take some of your advce on http://qmailrocks.thibs.com/

   View CommentView Comment

   Reply
2. Thibs says:

   August 14, 2011 at 11:49 am

   Firefox 5.0 Windows XP
   Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0

   Unfortunately, the qmailanalog-installer do not exists anymore under Debian Squeeze

   View CommentView Comment

   Reply
   • admin says:

     August 15, 2011 at 12:40 pm

     Epiphany 2.30.6 Debian GNU/Linux x64
     Mozilla/5.0 (X11; U; Linux x86_64; en-us) AppleWebKit/531.2+ (KHTML, like Gecko) Version/5.0 Safari/531.2+ Debian/squeeze (2.30.6-1) Epiphany/2.30.6

     Yes too pity, even the backports repo doesn’t contain the package. Maybe the old package for Lenny would be working fine ?

     View CommentView Comment

     Reply
3. Monjinul Mobin says:

   March 16, 2017 at 11:17 am

   Google Chrome 56.0.2924.87 Windows 8.1 x64 Edition
   Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

   Hey There. I found your blog in google,your posts are extremely well written. Thanks for the post.

   I have followed above instruction but when i run qmail-stats.py then getting below errors. Could you please help me.

   File “/usr/local/bin/qmail-stats.py”, line 102, in
   os.chdir( LOGFILE_PATH )
   OSError: [Errno 13] Permission denied: ‘/var/log/qmail/qmail-send/’

   in details

   Failures
   —————-
   sort: cannot read: +2: No such file or directory
   awk: write failure (Broken pipe)
   awk: close failed on file /dev/stdout (Broken pipe)
   Reasons for failure

   One line per reason for delivery failure. Information on each line:
   * del is the number of deliveries that ended for this reason.
   * xdelay is the total xdelay on those deliveries.

   del xdelay reason

   ***************************************************************
   Deferrals
   —————-
   sort: cannot read: +2: No such file or directory
   awk: close failed on file /dev/stdout (Broken pipe)
   Reasons for deferral

   One line per reason for deferral. Information on each line:
   * del is the number of deliveries that ended for this reason.
   * xdelay is the total xdelay on those deliveries.

   del xdelay reason

   ***************************************************************
   Top Ten Senders
   —————-
   sort: cannot read: +7: No such file or directory
   awk: write failure (Broken pipe)
   awk: close failed on file /dev/stdout (Broken pipe)
   * xdelay is the total xdelay incurred by this sender.
   * tries is the number of delivery attempts (success, failure, deferral).
   Senders
   * sbytes is the number of bytes successfully received from this sender.
   * recips is the number of recipients (success plus failure).
   * rbytes is the number of bytes from this sender, weighted by recipient.
   One line per sender. Information on each line:
   * mess is the number of messages sent by this sender.
   mess bytes sbytes rbytes recips tries xdelay sender
   * bytes is the number of bytes sent by this sender.

   ***************************************************************
   Top Ten Recipients
   —————-
   sort: cannot read: +4: No such file or directory
   awk: write failure (Broken pipe)
   awk: close failed on file /dev/stdout (Broken pipe)
   * xdelay is the total xdelay incurred by this recipient.
   * tries is the number of delivery attempts (success, failure, deferral).
   * sbytes is the number of bytes successfully delivered to this recipient.
   sbytes mess tries xdelay recipient
   * mess is the number of messages sent to this recipient (success plus failure).
   One line per recipient. Information on each line:
   Recipients

   View CommentView Comment

   Reply
   • admin says:

     March 16, 2017 at 4:20 pm

     Firefox 52.0 Windows 7 x64 Edition
     Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

     Hi Mobin,

     Is your /var/log/qmail/qmail-send/ directory existing and does it have proper permissions, could be your qmail log file directory is different?

     Regards,

     Georgi

     View CommentView Comment

     Reply
     • Monjinul Mobin says:

       March 19, 2017 at 8:07 am

       Google Chrome 56.0.2924.87 Windows 8.1 x64 Edition
       Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

       Hi Georgi

       Yes /var/log/qmail/qmail-send/ directory exist and its permission is set as qmaill nofiles. qmail-stats.py also have same permission. Pleas help me.

       Thanks

       View CommentView Comment

       Reply
4. Monjinul Mobin says:

   March 19, 2017 at 8:34 am

   Google Chrome 56.0.2924.87 Windows 8.1 x64 Edition
   Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

   Hi Georgi,

   Sorry it is actually working partially. Please see the below stats. It is only showing summary but not showing Top ten sender,receiver,Failures or Deferrals. Please help

   Completed messages: 1397
   Recipients for completed messages: 1645
   Total delivery attempts for completed messages: 1646
   Average delivery attempts per completed message: 1.17824
   Bytes in completed messages: 407985081
   Bytes weighted by success: 461962077
   Average message qtime (s): 1.88326

   Total delivery attempts: 1654
   success: 1544
   failure: 102
   deferral: 8
   Total ddelay (s): 1724.399932
   Average ddelay per success (s): 1.116839
   Total xdelay (s): 2421.575779
   Average xdelay per delivery attempt (s): 1.464072
   Time span (days): 0.0756242
   Average concurrency: 0.370615

   ***************************************************************

   Failures
   —————-
   sort: cannot read: +2: No such file or directory
   awk: write failure (Broken pipe)
   awk: close failed on file /dev/stdout (Broken pipe)
   Reasons for failure

   One line per reason for delivery failure. Information on each line:
   * del is the number of deliveries that ended for this reason.
   * xdelay is the total xdelay on those deliveries.

   del xdelay reason

   ***************************************************************
   Deferrals
   —————-
   sort: cannot read: +2: No such file or directory
   awk: close failed on file /dev/stdout (Broken pipe)
   Reasons for deferral

   One line per reason for deferral. Information on each line:
   * del is the number of deliveries that ended for this reason.
   * xdelay is the total xdelay on those deliveries.

   del xdelay reason

   ***************************************************************
   Top Ten Senders
   —————-
   sort: cannot read: +7: No such file or directory
   awk: write failure (Broken pipe)
   awk: close failed on file /dev/stdout (Broken pipe)
   * xdelay is the total xdelay incurred by this sender.
   * tries is the number of delivery attempts (success, failure, deferral).
   Senders
   * sbytes is the number of bytes successfully received from this sender.
   * recips is the number of recipients (success plus failure).
   * rbytes is the number of bytes from this sender, weighted by recipient.
   One line per sender. Information on each line:
   * mess is the number of messages sent by this sender.
   mess bytes sbytes rbytes recips tries xdelay sender
   * bytes is the number of bytes sent by this sender.

   ***************************************************************
   Top Ten Recipients
   —————-
   sort: cannot read: +4: No such file or directory
   awk: write failure (Broken pipe)
   awk: close failed on file /dev/stdout (Broken pipe)
   * xdelay is the total xdelay incurred by this recipient.
   * tries is the number of delivery attempts (success, failure, deferral).
   * sbytes is the number of bytes successfully delivered to this recipient.
   sbytes mess tries xdelay recipient
   * mess is the number of messages sent to this recipient (success plus failure).
   One line per recipient. Information on each line:
   Recipients

   View CommentView Comment

   Reply
   • admin says:

     March 20, 2017 at 11:56 am

     Firefox 52.0 Windows 7 x64 Edition
     Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

     Hi Mobin,

      

     Try to run the script with

     strace qmainanalog

     and see closely the output could be some log file expected under a location is not there but on a different location, check the script concent where the /var/log/qmail paths as described in script are matching yours.

     But anyways strace should tell you a bit more, Hope this helps.
      

     Best
     Georgi

     View CommentView Comment

     Reply
5. Colin says:

   June 3, 2022 at 2:30 am

   Google Chrome 102.0.0.0 Windows 10 x64 Edition
   Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.0.0 Safari/537.36

   Hello

   Those failures with cannot read +4 and similar messages are caused by old deprecates parameters being used with the sort command used in most of the z* scripts in the qmailanalog package. Have a look here

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578395

   at a Debian bug report for some more information. I updated my qmailanalog pscripts as indicated and it fixed it for me..

   Regards

    

   Colin

   View CommentView Comment

   Reply