smeserver-qmHandle

psc

151
+0/-0

smeserver-qmHandle

« on: August 16, 2004, 10:14:14 AM »

Available here:

http://www.saco-service.de/sme/smeserver-saco-qmHandle/

To manage the qmail queue

Installation should now smeserver 6.x "clean".

Peter

Logged

First, solve the problem. Then, write the code.

pietfriet

Re: smeserver-qmHandle

« Reply #1 on: August 26, 2005, 10:02:15 PM »

Quote from: "psc"

Available here:

http://www.saco-support.de/sme/smeserver-qmHandle/

This link doesn't work anymore. It is also listed at the Contribs SME Server Download section.

I am facing the following problem:

I tried to send an email to a friend with a rather big attachment (7 MB) The provider of my friend (XS4ALL) bounced my e-mail (Filesize of attachment to big). Now this e-mail is stuck in my server. SME is trying again and again to send the e-mail and it won't stop.

I am now pretty mad I am at the point of shooting the damn e-mail out of my server like a duck...

Is there somebody that can tell me how to control and acces the "Outbox" (I am not sure how to call this) of my e-mail server..

Thank you in advance

Best regards,

Sander

Logged

Franco

1,171
+0/-0

smeserver-qmHandle

« Reply #2 on: August 26, 2005, 10:57:38 PM »

Install qmHandle http://mirror.contribs.org/smeserver/contribs/saco/contrib/e-smith-qmHandle/e-smith-qmHandle-1.0.0-7.noarch.rpm

and issued the command

Code: [Select]

 
qmHandle -D

Warning, this will empty the entire queue

Logged

pietfriet

smeserver-qmHandle

« Reply #3 on: August 27, 2005, 12:58:30 AM »

thank you, going to run the rpm now

Logged

pietfriet

Nope, didn't fixef the problem

« Reply #4 on: August 27, 2005, 02:12:39 AM »

A friend advised me to give some more detailed information

SME version: 6.5

E-mail I get (the bounce)

Code: [Select]

The original message was received at Wed, 24 Aug 2005 19:56:46 +0200
from localhost [127.0.0.1]

   ----- The following addresses had permanent fatal errors -----
<000@planet.nl>
    (reason: 550 5.2.3 channel size limit exceeded: 000@planet.nl)

   ----- Transcript of session follows -----
... while talking to mail.wxs.nl.:
>>> DATA
<<< 550 5.2.3 channel size limit exceeded: 000@planet.nl
550 5.1.1 <000@planet.nl>... User unknown
<<< 554 5.5.0 No recipients have been specified.

I am using a combination of Fetchmail and qmail

The logs

maillog.20050822011211

Code: [Select]

Aug 27 01:32:35 saturn fetchmail[15396]: client/server protocol error while fetching from pop.skynet.be 
Aug 27 01:32:35 saturn fetchmail[15396]: Query status=4 (PROTOCOL) 
Aug 27 01:47:32 saturn fetchmail[15565]: client/server protocol error while fetching from pop.skynet.be 
Aug 27 01:47:32 saturn fetchmail[15565]: Query status=4 (PROTOCOL)

qmail/current

Code: [Select]

2005-06-30 11:59:21.281440500 status: local 3/10 remote 0/20
2005-06-30 11:59:21.281443500 delivery 10: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
2005-06-30 11:59:21.281448500 status: local 2/10 remote 0/20
2005-06-30 11:59:21.281451500 delivery 11: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
2005-06-30 11:59:21.281456500 status: local 1/10 remote 0/20

smtpfront-qmail/current

Code: [Select]

2005-08-27 01:30:05.246246500 smtpfront-qmail[15421]: EHLO localhost
2005-08-27 01:30:05.284144500 smtpfront-qmail[15421]: MAIL FROM:<MAILER-DAEMON@outmx009.isp.belgacom.be> SIZE=10438107
2005-08-27 01:30:05.284531500 smtpfront-qmail[15421]: RCPT TO:<postmaster@nodomain.net>
2005-08-27 01:32:35.382163500 smtpfront-qmail[15421]: Accepted message qp 15422 bytes 10304594
2005-08-27 01:32:35.386411500 smtpfront-qmail[15421]: bytes in: 10438483 bytes out: 283
2005-08-27 01:32:35.386843500 tcpsvd: info: end 15421 exit 0
2005-08-27 01:32:35.386851500 tcpsvd: info: status 0/40
2005-08-27 01:45:04.054930500 tcpsvd: info: status 1/40
2005-08-27 01:45:04.055075500 tcpsvd: info: pid 15590 from 127.0.0.1
2005-08-27 01:45:04.055355500 tcpsvd: info: concurrency 15590 127.0.0.1 1/4
2005-08-27 01:45:04.055360500 tcpsvd: info: start 15590 saturn.nodomain:127.0.0.1 ::127.0.0.1:36714 ./peers/127.0.0.1
2005-08-27 01:45:04.066498500 smtpfront-qmail[15590]: EHLO localhost
2005-08-27 01:45:04.099852500 smtpfront-qmail[15590]: MAIL FROM:<MAILER-DAEMON@nodomain.net> SIZE=10438107
2005-08-27 01:45:04.100267500 smtpfront-qmail[15590]: RCPT TO:<postmaster@nodomain.net>
2005-08-27 01:47:32.667103500 smtpfront-qmail[15590]: Accepted message qp 15591 bytes 10304594
2005-08-27 01:47:32.667209500 smtpfront-qmail[15590]: bytes in: 10438483 bytes out: 283
2005-08-27 01:47:32.667214500 tcpsvd: info: end 15590 exit 0
2005-08-27 01:47:32.667217500 tcpsvd: info: status 0/40
2005-08-27 02:00:05.411085500 tcpsvd: info: status 1/40
2005-08-27 02:00:05.411241500 tcpsvd: info: pid 15789 from 127.0.0.1
2005-08-27 02:00:05.411543500 tcpsvd: info: concurrency 15789 127.0.0.1 1/4
2005-08-27 02:00:05.411550500 tcpsvd: info: start 15789 saturn.nodomain.net:127.0.0.1 ::127.0.0.1:36735 ./peers/127.0.0.1
2005-08-27 02:00:05.452605500 smtpfront-qmail[15789]: EHLO localhost
2005-08-27 02:00:05.485715500 smtpfront-qmail[15789]: MAIL FROM:<MAILER-DAEMON@nodomain.net> SIZE=10438107
2005-08-27 02:00:05.486115500 smtpfront-qmail[15789]: RCPT TO:<postmaster@nodomain.net>
2005-08-27 02:02:37.335080500 smtpfront-qmail[15789]: Accepted message qp 15790 bytes 10304594
2005-08-27 02:02:37.337561500 smtpfront-qmail[15789]: bytes in: 10438483 bytes out: 283
2005-08-27 02:02:37.337571500 tcpsvd: info: end 15789 exit 0
2005-08-27 02:02:37.337575500 tcpsvd: info: status 0/40

I think this is pretty much al the information there is in the logs on e-mails.

I am really stuck in this, been looking al over the internet/ contribs.org for a solution...

Im desperate (spelled correct?)

Logged

psc

151
+0/-0

New Version

« Reply #5 on: August 28, 2005, 11:30:42 AM »

The new Version can be found here:
http://www.saco-service.de/sme/smeserver-saco-qmHandle/

Logged

First, solve the problem. Then, write the code.

pietfriet

smeserver-qmHandle

« Reply #6 on: September 01, 2005, 03:55:24 PM »

I installed the new version but qmHandle give's no information

zero messages in queue

Logged

CharlieBrady

6,918
+3/-0

smeserver-qmHandle

« Reply #7 on: September 01, 2005, 05:03:06 PM »

Quote from: "stuntshell"

Install qmHandle http://mirror.contribs.org/smeserver/contribs/saco/contrib/e-smith-qmHandle/e-smith-qmHandle-1.0.0-7.noarch.rpm

and issued the command
Code: [Select]
qmHandle -D

Warning, this will empty the entire queue

So you should never do that, right? Just delete messages which need to be deleted.

Logged

CharlieBrady

6,918
+3/-0

Re: Nope, didn't fixef the problem

« Reply #8 on: September 01, 2005, 05:15:30 PM »

Quote from: "pietfriet"

I am using a combination of Fetchmail and qmail

fetchmail should be avoided wherever possible.

Quote

Code: [Select]
2005-06-30 11:59:21.281440500 status: local 3/10 remote 0/20 2005-06-30 11:59:21.281443500 delivery 10: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/ 2005-06-30 11:59:21.281448500 status: local 2/10 remote 0/20 2005-06-30 11:59:21.281451500 delivery 11: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/ 2005-06-30 11:59:21.281456500 status: local 1/10 remote 0/20

This indicates that you have a missing maildir, or one with the wrong permissions. This is preventing local delivery of some messages. You need to look earlier in the log file to identify which deliveries are not succeeding. The mail log analysis panel might help you.

Quote

Code: [Select]
2005-08-27 01:30:05.246246500 smtpfront-qmail[15421]: EHLO localhost 2005-08-27 01:30:05.284144500 smtpfront-qmail[15421]: MAIL FROM:<MAILER-DAEMON@outmx009.isp.belgacom.be> SIZE=10438107 2005-08-27 01:30:05.284531500 smtpfront-qmail[15421]: RCPT TO:<postmaster@nodomain.net> 2005-08-27 01:32:35.382163500 smtpfront-qmail[15421]: Accepted message qp 15422 bytes 10304594 2005-08-27 01:32:35.386411500 smtpfront-qmail[15421]: bytes in: 10438483 bytes out: 283 2005-08-27 01:32:35.386843500 tcpsvd: info: end 15421 exit 0 2005-08-27 01:32:35.386851500 tcpsvd: info: status 0/40 2005-08-27 01:45:04.054930500 tcpsvd: info: status 1/40 2005-08-27 01:45:04.055075500 tcpsvd: info: pid 15590 from 127.0.0.1 2005-08-27 01:45:04.055355500 tcpsvd: info: concurrency 15590 127.0.0.1 1/4 2005-08-27 01:45:04.055360500 tcpsvd: info: start 15590 saturn.nodomain:127.0.0.1 ::127.0.0.1:36714 ./peers/127.0.0.1 2005-08-27 01:45:04.066498500 smtpfront-qmail[15590]: EHLO localhost 2005-08-27 01:45:04.099852500 smtpfront-qmail[15590]: MAIL FROM:<MAILER-DAEMON@nodomain.net> SIZE=10438107 2005-08-27 01:45:04.100267500 smtpfront-qmail[15590]: RCPT TO:<postmaster@nodomain.net> 2005-08-27 01:47:32.667103500 smtpfront-qmail[15590]: Accepted message qp 15591 bytes 10304594 2005-08-27 01:47:32.667209500 smtpfront-qmail[15590]: bytes in: 10438483 bytes out: 283 2005-08-27 01:47:32.667214500 tcpsvd: info: end 15590 exit 0 2005-08-27 01:47:32.667217500 tcpsvd: info: status 0/40 2005-08-27 02:00:05.411085500 tcpsvd: info: status 1/40 2005-08-27 02:00:05.411241500 tcpsvd: info: pid 15789 from 127.0.0.1 2005-08-27 02:00:05.411543500 tcpsvd: info: concurrency 15789 127.0.0.1 1/4 2005-08-27 02:00:05.411550500 tcpsvd: info: start 15789 saturn.nodomain.net:127.0.0.1 ::127.0.0.1:36735 ./peers/127.0.0.1 2005-08-27 02:00:05.452605500 smtpfront-qmail[15789]: EHLO localhost 2005-08-27 02:00:05.485715500 smtpfront-qmail[15789]: MAIL FROM:<MAILER-DAEMON@nodomain.net> SIZE=10438107 2005-08-27 02:00:05.486115500 smtpfront-qmail[15789]: RCPT TO:<postmaster@nodomain.net> 2005-08-27 02:02:37.335080500 smtpfront-qmail[15789]: Accepted message qp 15790 bytes 10304594 2005-08-27 02:02:37.337561500 smtpfront-qmail[15789]: bytes in: 10438483 bytes out: 283 2005-08-27 02:02:37.337571500 tcpsvd: info: end 15789 exit 0 2005-08-27 02:02:37.337575500 tcpsvd: info: status 0/40

I suspect from this log file that you have a mail loop somehow. Do you, for instance, have your postmaster mail forwarded to an outside email address? In any case, you need to determine why you are seeing this message again and again.

fetchmail is also at fault here, it should be using <> as the "mail from" address.

Quote

Im desperate (spelled correct?)

"desperate" is, by "I'm" isn't.

Finally, please repeat after me: I will not send 10MB email messages.

Logged

Franco

1,171
+0/-0

smeserver-qmHandle

« Reply #9 on: September 01, 2005, 05:26:28 PM »

I meant to say that in the case that he knows that only 01 message is in queue. This new version of qmail is cool that you can actually read the messages and delete from it.
And I wouldn't say "never". I've read so many cases here of people not securing their systems (meaning opening to the world)that they ended with 25.000 messages in queue. The -D option will get them back quickly

Logged

albatroz

159
+0/-0

smeserver-qmHandle

« Reply #10 on: April 05, 2006, 02:27:04 AM »

I tried to install qmHandle, but I am getting these error messages

Is the first time this happens to me as I have installed qmHandle previously in other servers without problems

error: error(-30981) storing record en-us into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record etc into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record e-smith into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record web into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record functions into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record qmh into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record web into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record functions into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record qmh into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record panels into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record manager into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record cgi-bin into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record qmh into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record bin into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record qmHandle into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record qmHandle-1.0.0 into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record GPL into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record HISTORY into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record README into Basenames
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Group index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Requirename index using db3 - (-30981)
error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record smeserver-saco-qmHandle into Providename
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Dirnames index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Requireversion index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Provideversion index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Installtid index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sigmd5 index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sha1header index using db3 - (-30981)
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Filemd5s index using db3 - (-30981)
error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Triggername index using db3 - (-30981)
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db_env_create: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from dbenv->remove: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: Page 1925 encountered a second time on free list
error: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database verification failed

Logged

Tib

571
+0/-0

smeserver-qmHandle

« Reply #11 on: April 05, 2006, 09:54:16 AM »

albatroz,

What ver did you install ... it worked fine for me ... even installed it onto a machine today for someone on SME7 RC1

http://www.saco-service.de/sme/smeserver-saco-qmHandle/

If thats the one you installed then I have no idea.

Regards,

Tib

Logged

Franco

1,171
+0/-0

smeserver-qmHandle

« Reply #12 on: April 05, 2006, 02:09:12 PM »

1.2.1 is the latest, you installed a 1.0.0...

Logged

CharlieBrady

6,918
+3/-0

smeserver-qmHandle

« Reply #13 on: April 05, 2006, 04:42:56 PM »

Quote from: "albatroz"

I tried to install qmHandle, but I am getting these error messages

Is the first time this happens to me as I have installed qmHandle previously in other servers without problems

error: error(-30981) storing record en-us into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
...

Those errors indicate corruption in your rpm database. Google might indicate some method to repair those problems. If you can't repair, you can backup/fresh install/restore.

Logged