Loading ...
Sorry, an error occurred while loading the content.

Re: FW: 170000 messages in my queue

Expand Messages
  • Noel Jones
    ... Are these legit message? Are they waiting on amavisd-new or on final delivery? ... Splitting your err, warn, and info logs makes reading the logs much
    Message 1 of 5 , Sep 9, 2013
    • 0 Attachment
      On 9/9/2013 10:19 AM, Jumping Mouse wrote:
      >
      >
      > --------------------------------------------------------------------
      > From: kafriki@...
      > To: postfix-users@...
      > Subject: 170000 messages in my queue
      > Date: Mon, 9 Sep 2013 11:18:17 -0400
      >
      > Hello everyone,
      >
      > I am using postfix 2.5.1 with amavisd-new. which has been working
      > well for years. I have around 170000 messages stuck in my queue
      > and flushing the queue does not help.
      >

      Are these legit message? Are they waiting on amavisd-new or on
      final delivery?


      > The only changes I made to the config is adding around 100 aliases.
      >
      > Can anyone help me troubleshoot this?
      >
      >
      > Here are few entries from my:
      >
      > mail.err log

      Splitting your err, warn, and info logs makes reading the logs much
      harder.


      >
      > Sep 9 08:30:37 mail spamc[20483]: skipped message, greater than max message size (512000 bytes)
      > Sep 9 08:57:24 mail spamc[22585]: skipped message, greater than max message size (512000 bytes)

      Why are you getting messages from spamc if you're using amavisd-new?
      Amavisd-new does not use spamc/spamd. Have you somehow configured
      both amavisd-new and spamc, and filtering messages twice? or maybe
      you're not really using amavisd-new; I don't see any messages from
      amavisd in your log snippings.


      >
      >
      > mail.warn
      >
      >
      > Sep 9 11:02:18 mail spamd[2071]: bayes: cannot open bayes databases /home/journal/.spamassassin/bayes_* R/W: lock failed: File exists

      This looks like a problem with your spam filter. Maybe it's taking
      too long to scan messages.


      > Sep 9 11:03:43 mail postfix/qmgr[1745]: warning: mail for gapps.collaborative.org is using up 10888 of 20000 active queue entries
      > Sep 9 11:03:43 mail postfix/qmgr[1745]: warning: this may slow down other mail deliveries

      This message is "normal" when you have lots of mail queued for a
      specific destination; you need to find the underlying cause.

      > Sep 9 11:04:29 mail postfix/qmgr[1745]: warning: mail for mail.collaborative.org is using up 9282 of 20000 active queue entries
      > Sep 9 11:04:29 mail postfix/qmgr[1745]: warning: this may slow down other mail deliveries
      > Sep 9 11:04:29 mail postfix/qmgr[1745]: warning: you may need to increase the main.cf local_destination_concurrency_limit from 2

      This message may indicate slow local delivery, or it might be due to
      slow spam scanning.



      >
      > Mail.log
      >
      > Sep 9 11:14:28 mail postfix/qmgr[1745]: C2E6C1233338: from=<audit2@...>, size=6286, nrcpt=1 (queue active)
      > Sep 9 11:14:28 mail postfix/smtp[3941]: 62A551231A9F: to=<audit@...>, orig_to=<audit@...>, relay=ALT2.ASPMX.L.GOOGLE.com[173.194.73.27]:25, delay=218791, delays=217847/940/3.4/0.67, dsn=2.0.0, status=sent (250 2.0.0 OK 1378739668 o10si3267366vco.65 - gsmtp)

      This message spent 2+ days waiting in the queue, but only seconds to
      actually deliver. Obviously a bottleneck somewhere.


      > Sep 9 11:14:28 mail postfix/qmgr[1745]: 76E081237644: from=<audit2@...>, size=166776, nrcpt=2 (queue active)
      > Sep 9 11:14:28 mail postfix/smtp[3752]: certificate verification failed for aspmx.l.google.com[74.125.142.27]:25: untrusted issuer /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
      > Sep 9 11:14:28 mail postfix/smtp[3843]: 21BB3125958B: to=<audit2@...>, orig_to=<audit2@...>, relay=ASPMX.L.GOOGLE.com[74.125.142.27]:25, delay=632118, delays=631173/943/1.3/0.53, dsn=2.0.0, status=sent (250 2.0.0 OK 1378739668 c15si7189163igv.26 - gsmtp)
      > Sep 9 11:14:28 mail postfix/qmgr[1745]: 21BB3125958B: removed
      > Sep 9 11:14:28 mail postfix/smtp[3780]: 27157124D20E: to=<audit@...>, orig_to=<audit@...>, relay=ASPMX.L.GOOGLE.com[74.125.142.27]:25, delay=675178, delays=674233/939/1.6/4.4, dsn=2.0.0, status=sent (250 2.0.0 OK 1378739668 df4si14521934icb.28 - gsmtp)
      > Sep 9 11:14:28 mail postfix/qmgr[1745]: 79149125FB7B: from=<audit2@...>, size=7879, nrcpt=2 (queue active)
      > Sep 9 11:14:28 mail postfix/qmgr[1745]: 27157124D20E: removed

      These spent even longer -- about a week -- waiting, but still only
      took seconds to deliver.


      I think spamc logs how long it takes to scan, but don't see that
      included. Maybe spamd needs to be restarted?


      These might help:
      http://www.postfix.org/QSHAPE_README.html
      http://www.postfix.org/TUNING_README.html
      http://www.postfix.org/DEBUG_README.html


      If you need more help:
      http://www.postfix.org/DEBUG_README.html#mail



      -- Noel Jones
    • Jumping Mouse
      ... Yes legit messages. not sure what they are waiting for. ... yeah.. that s how I get them through webmin.. I see your point though. ... I realized I
      Message 2 of 5 , Sep 9, 2013
      • 0 Attachment


        > Date: Mon, 9 Sep 2013 13:45:26 -0500
        > From: njones@...
        > To: postfix-users@...
        > Subject: Re: FW: 170000 messages in my queue
        >
        > On 9/9/2013 10:19 AM, Jumping Mouse wrote:
        > >
        > >
        > > --------------------------------------------------------------------
        > > From: kafriki@...
        > > To: postfix-users@...
        > > Subject: 170000 messages in my queue
        > > Date: Mon, 9 Sep 2013 11:18:17 -0400
        > >
        > > Hello everyone,
        > >
        > > I am using postfix 2.5.1 with amavisd-new. which has been working
        > > well for years. I have around 170000 messages stuck in my queue
        > > and flushing the queue does not help.
        > >
        >
        > Are these legit message? Are they waiting on amavisd-new or on
        > final delivery?

        Yes legit messages.  not sure what they are waiting for. 


        >
        >
        > > The only changes I made to the config is adding around 100 aliases.
        > >
        > > Can anyone help me troubleshoot this?
        > >
        > >
        > > Here are few entries from my:
        > >
        > > mail.err log
        >
        > Splitting your err, warn, and info logs makes reading the logs much
        > harder.


        yeah.. that's how I get them through webmin.. I see your point though. 

        >
        >
        > >
        > > Sep 9 08:30:37 mail spamc[20483]: skipped message, greater than max message size (512000 bytes)
        > > Sep 9 08:57:24 mail spamc[22585]: skipped message, greater than max message size (512000 bytes)
        >
        > Why are you getting messages from spamc if you're using amavisd-new?
        > Amavisd-new does not use spamc/spamd. Have you somehow configured
        > both amavisd-new and spamc, and filtering messages twice? or maybe
        > you're not really using amavisd-new; I don't see any messages from
        > amavisd in your log snippings.

        I realized I actually turned off Amavisd filtering a while ago.  So I am not using Amavisd.  

        >
        >
        > >
        > >
        > > mail.warn
        > >
        > >
        > > Sep 9 11:02:18 mail spamd[2071]: bayes: cannot open bayes databases /home/journal/.spamassassin/bayes_* R/W: lock failed: File exists
        >
        > This looks like a problem with your spam filter. Maybe it's taking
        > too long to scan messages.

        Not sure why it is still filtering spam I have turned filtering off. 


        >
        >
        > > Sep 9 11:03:43 mail postfix/qmgr[1745]: warning: mail for gapps.collaborative.org is using up 10888 of 20000 active queue entries
        > > Sep 9 11:03:43 mail postfix/qmgr[1745]: warning: this may slow down other mail deliveries
        >
        > This message is "normal" when you have lots of mail queued for a
        > specific destination; you need to find the underlying cause.


        Yes still looking. 



        >
        > > Sep 9 11:04:29 mail postfix/qmgr[1745]: warning: mail for mail.collaborative.org is using up 9282 of 20000 active queue entries
        > > Sep 9 11:04:29 mail postfix/qmgr[1745]: warning: this may slow down other mail deliveries
        > > Sep 9 11:04:29 mail postfix/qmgr[1745]: warning: you may need to increase the main.cf local_destination_concurrency_limit from 2
        >
        > This message may indicate slow local delivery, or it might be due to
        > slow spam scanning.

        looking into this. 


        >
        >
        > >
        > > Mail.log
        > >
        > > Sep 9 11:14:28 mail postfix/qmgr[1745]: C2E6C1233338: from=<audit2@...>, size=6286, nrcpt=1 (queue active)
        > > Sep 9 11:14:28 mail postfix/smtp[3941]: 62A551231A9F: to=<audit@...>, orig_to=<audit@...>, relay=ALT2.ASPMX.L.GOOGLE.com[173.194.73.27]:25, delay=218791, delays=217847/940/3.4/0.67, dsn=2.0.0, status=sent (250 2.0.0 OK 1378739668 o10si3267366vco.65 - gsmtp)
        >
        > This message spent 2+ days waiting in the queue, but only seconds to
        > actually deliver. Obviously a bottleneck somewhere.

        Yes



        >
        >
        > > Sep 9 11:14:28 mail postfix/qmgr[1745]: 76E081237644: from=<audit2@...>, size=166776, nrcpt=2 (queue active)
        > > Sep 9 11:14:28 mail postfix/smtp[3752]: certificate verification failed for aspmx.l.google.com[74.125.142.27]:25: untrusted issuer /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
        > > Sep 9 11:14:28 mail postfix/smtp[3843]: 21BB3125958B: to=<audit2@...>, orig_to=<audit2@...>, relay=ASPMX.L.GOOGLE.com[74.125.142.27]:25, delay=632118, delays=631173/943/1.3/0.53, dsn=2.0.0, status=sent (250 2.0.0 OK 1378739668 c15si7189163igv.26 - gsmtp)
        > > Sep 9 11:14:28 mail postfix/qmgr[1745]: 21BB3125958B: removed
        > > Sep 9 11:14:28 mail postfix/smtp[3780]: 27157124D20E: to=<audit@...>, orig_to=<audit@...>, relay=ASPMX.L.GOOGLE.com[74.125.142.27]:25, delay=675178, delays=674233/939/1.6/4.4, dsn=2.0.0, status=sent (250 2.0.0 OK 1378739668 df4si14521934icb.28 - gsmtp)
        > > Sep 9 11:14:28 mail postfix/qmgr[1745]: 79149125FB7B: from=<audit2@...>, size=7879, nrcpt=2 (queue active)
        > > Sep 9 11:14:28 mail postfix/qmgr[1745]: 27157124D20E: removed
        >
        > These spent even longer -- about a week -- waiting, but still only
        > took seconds to deliver.
        >
        >
        > I think spamc logs how long it takes to scan, but don't see that
        > included. Maybe spamd needs to be restarted?


        Mail should not be filtered at the moment, will look at what is going on. 


        >
        >
        > These might help:
        > http://www.postfix.org/QSHAPE_README.html
        > http://www.postfix.org/TUNING_README.html
        > http://www.postfix.org/DEBUG_README.html
        >
        >
        > If you need more help:
        > http://www.postfix.org/DEBUG_README.html#mail
        >
        >
        >
        > -- Noel Jones



        Thanks Noel. 

        .   




      • John Allen
        When you say you turned amavisd off, how did you turn it off?
        Message 3 of 5 , Sep 9, 2013
        • 0 Attachment
          When you say you turned amavisd off, how did you turn it off?
        • James Griffin
          ... Do you have procmail piping messages to spamc? -- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
          Message 4 of 5 , Sep 10, 2013
          • 0 Attachment
            !-- On Mon 9.Sep'13 at 21:39:07 BST, Jumping Mouse (kafriki@...), wrote:

            > I realized I actually turned off Amavisd filtering a while ago. So I am not using Amavisd.

            Do you have procmail piping messages to spamc?
            --


            James Griffin: jmz at kontrol.kode5.net

            A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
          Your message has been successfully submitted and would be delivered to recipients shortly.