Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: [...] But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the new msg line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: qmail-queue question
Edward, I've had problems with qmail-remote hanging - it had nothing to do with the queue lifetime, but with some code in qmail-remote failing, possibly due to an O/S bug. A fix which works for me is to enable socket keep-alives. This will kill the socket if it has died after about 2-3 hours. I've put a patch on the web at http://www.duff.org/qmail/ Richard -Original Message- From: Edward McLain [mailto:[EMAIL PROTECTED]] On a side note, is there any reason that qmail-remote should start up and then just sit there connected to a remote host for like 6 or 7 hours trying to send one email? I get this all the freaking time and I'm just wandering what exactly the freaking thing is doing? (although this problem only really seems to occur with mindspring.com, yet if I telnet to port 25 of mindsprings mail server and send the same message through telnet to the same user, from the same user as the one qmail's trying to send it works just fine and I don't get any errors or return codes.)
RE: qmail-queue question
OK... Let me explain this a little bit better and maybe clear some things up. 1. I've been using unix for about 8 years now and when someone says to restart a service or proggy after changing a config file, by god that service or proggy gets restarted, even if it takes a kill -9 or killall -9 to do it. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) 4. I am a freaking consultant and I wouldn't bother this mailing list unless it was something worthwhile. But when all the instructions fail, and searching through code, and rewriting part of qmail-remote output actual logging, this is generally the place to turn to. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, that is what mailing list are for aren't they. Arrogance is nice and all, but what good does it do you an empty room when everyone has left you. Any real help on this issue would be appreciated from anyone. Later, Ed McLain -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 9:58 AM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question Edward McLain [EMAIL PROTECTED] wrote: [...] But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the new msg line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: OK... Let me explain this a little bit better and maybe clear some things up. Okay. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. This can cause qmail-queue to not be run, but not qmail-remote to crash. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. That doesn't give all the information about that message; in particular, delivery status lines don't contain the message number, only the delivery number, which you get from the starting delivery lines. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, What do you think I'm doing? You're wasting everyone's time by posting incomplete reports -- I'm trying to help you post better reports, so we can _help_ you. You want better service than that? Call Russ Nelson -- he'll come to your house and hold your hand, given sufficient incentive. For free, it doesn't get any better than this. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards.
RE: qmail-queue question
-Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the daemons to stop loading and running without editing /etc/inittab and commenting out the line that runs the svcscanboot and doing a kill -HUP 1. Then I have to do a kill or killall on all the qmail daemons to actually shut it down. Later, ed
Re: qmail-queue question
On Thu, Aug 09, 2001 at 12:39:28PM -0500, Edward McLain allegedly wrote: -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. It probably would have been helpful if you'd told us about this at the start. It seemed like you were trying to suggest that the log entry never existed. I guess that's a lesson for next time. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Mysteriously? Since we've stressed the importance of looking at logs for answers, I'm sure you've checked the logs to solve the mystery. What did they say? I'm sure if you bother, you'll see that it's not a mystery at all. Unless of course you kill -9 qmail-send, but no one or no docs have ever told you to do this, right? In any event, as I said in the the last post; queuelifetime applies *after* the last delivery attempt has exited. It's almost certainly the case that you killed qmail-remote (or it exited of its own accord) at which point qmail-send would notice that queuelifetime is exceeded and bounce the mail. The logs show this stuff by the way. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the It always works. But qmail-send won't exit until all current deliveries have exited - in fact it logs an entry each time an outstanding delivery completes. Did you see different when you checked the logs? If so, show us. Edward, for someone with 8 years experience, you should rejoice that so many of your mysteries and misunderstandings can be solved by examining and understanding the logs. If the log messages are a mystery to you, there are plenty of archived posts explaining the messages. Regards.
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? No -- that is the proper way to stop qmail with daemontools. This doesn't seem to always work [...] Nope -- it always works. If not, you didn't install daemontools and your /service directories properly. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: qmail-queue question
.s:@40003b72c33a3620be2c delivery 26: deferral: qmail-remote_crashed./ [root@mail send]# Ok.. so qmail-remote crashed.. but why? It had also been running for over 3 hours? Well to test it out I did the following: [root@mail qmail]# telnet mx09.mindspring.com 25 Trying 207.69.200.36... Connected to mx09.mindspring.com. Escape character is '^]'. 220 pickering.mail.mindspring.net EL_3_4_0 /EL_3_4_0 ESMTP Earthlink Mail Service Thu, 9 Aug 2001 16:20:40 -0400 (EDT) helo mail.highspd.net 250 pickering.mail.mindspring.net Hello mail.highspd.net [208.62.90.230], please to meet you mail from: [EMAIL PROTECTED] 250 [EMAIL PROTECTED] Sender ok rcpt to: [EMAIL PROTECTED] 250 [EMAIL PROTECTED]... Recipient ok data 354 Enter mail, end with . on a line by itself this is a test. please disregard . 250 tn5s62.1dc.37kbi14 Message accepted for delivery quit 221 pickering.mail.mindspring.net closing connection Connection closed by foreign host. Ok.. so I can send mail directly just fine.. So what in the heck is going on here? This is what is puzzling me the most..? BTW.. this was happening with stock qmail also before I patched it with the qmail-queue patch for qmailscanner. Any ideas? Ed McLain -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 2:04 PM To: Edward McLain Cc: [EMAIL PROTECTED] Subject: Re: qmail-queue question On Thu, Aug 09, 2001 at 12:39:28PM -0500, Edward McLain allegedly wrote: -Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a new msg log entry. Where is it? There was no new msg log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. It probably would have been helpful if you'd told us about this at the start. It seemed like you were trying to suggest that the log entry never existed. I guess that's a lesson for next time. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Mysteriously? Since we've stressed the importance of looking at logs for answers, I'm sure you've checked the logs to solve the mystery. What did they say? I'm sure if you bother, you'll see that it's not a mystery at all. Unless of course you kill -9 qmail-send, but no one or no docs have ever told you to do this, right? In any event, as I said in the the last post; queuelifetime applies *after* the last delivery attempt has exited. It's almost certainly the case that you killed qmail-remote (or it exited of its own accord) at which point qmail-send would notice that queuelifetime is exceeded and bounce the mail. The logs show this stuff by the way. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the It always works. But qmail-send won't exit until all current deliveries have exited - in fact it logs an entry each time an outstanding delivery completes. Did you see different when you checked the logs? If so, show us. Edward, for someone with 8 years experience, you should rejoice that so many of your mysteries and misunderstandings can be solved by examining and understanding the logs. If the log messages are a mystery to you, there are plenty of archived posts explaining the messages. Regards.
Re: qmail-queue question
Ok.. so as someone pointed out I have to now search by the deliver number.. So I ran: [root@mail send]# grep delivery 366 * | /usr/local/bin/tai64nlocal 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery 366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so the last attempt started at 1:41PM.. So what happened to the one before it? [root@mail send]# grep delivery 26: * | /usr/local/bin/tai64nlocal 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery 26: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 13:41:28.533103500.s:@40003b72c33a3620be2c delivery 26: deferral: qmail-remote_crashed./ [root@mail send]# Ok.. so qmail-remote crashed.. but why? Unless something very unusual is happening to your system, I'd say that someone or something killed it. An unpatched qmail-remote has no record of crashing in the last, oh, 3 years of people using it. It had also been running for over 3 hours? That's not necessarily a problem. Mail is allowed to get stuck. Is any mail getting thru to these sites or are they all failing? Well to test it out I did the following: [root@mail qmail]# telnet mx09.mindspring.com 25 Trying 207.69.200.36... Connected to mx09.mindspring.com. Escape character is '^]'. 220 pickering.mail.mindspring.net EL_3_4_0 /EL_3_4_0 ESMTP Earthlink Mail Service Thu, 9 Aug 2001 16:20:40 -0400 (EDT) helo mail.highspd.net 250 pickering.mail.mindspring.net Hello mail.highspd.net [208.62.90.230], please to meet you mail from: [EMAIL PROTECTED] 250 [EMAIL PROTECTED] Sender ok rcpt to: [EMAIL PROTECTED] 250 [EMAIL PROTECTED]... Recipient ok data 354 Enter mail, end with . on a line by itself this is a test. please disregard . 250 tn5s62.1dc.37kbi14 Message accepted for delivery quit 221 pickering.mail.mindspring.net closing connection Connection closed by foreign host. Ok.. so I can send mail directly just fine.. So what in the heck is going on here? This is what is puzzling me the most..? Hard to say. It could be that the contents of the mail are a problem for mindspring, are they large? Do they have binary data? It could be that qmail-remote is connecting to an MX that's particularly slow or dead. It could be that you have an smtproutes entry for that domain that points incorrectly. BTW.. this was happening with stock qmail also before I patched it with the qmail-queue patch for qmailscanner. If you are saying you are sure that qmail-remote was crashing with a stock qmail install, then I'd be highly suspicious of a library/compiler/OS problem. I know that might sound like a cop-out, but a crashing qmail-remote is virtually unheard of. It's also possible that there is some sort of system resource that is becoming unavailable causing the kernel to kill the qmail-remote. Does this happen to all qmail-remotes or only those sending to mindspring? Does it happen to all qmail-remotes or only those that run for a long time? If you can reliably determine which ones are going to crash in advance of them crashing, then do a system call trace on one of them to see why it's dying. Show us the trace. Regards.
Re: qmail-queue question
Edward McLain [EMAIL PROTECTED] wrote: Ok.. so qmail-remote crashed.. but why? Who knows? Did you kill it? It had also been running for over 3 hours? So? Long messages to a slow host can do this. Well to test it out I did the following: [...] You didn't use proper SMTP syntax, which qmail-remote would have. Who says you connected to the same machine as qmail-remote did? mx09.mindspring.com could be a cluster of machines sitting behind a load balancer. mail from: [EMAIL PROTECTED] rcpt to: [EMAIL PROTECTED] This isn't proper SMTP. Any ideas? Just one: stop worrying until you have evidence of an actual problem. Everything you've described so far can be completely normal behaviour. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue and custom reject message
On Sat, Jul 28, 2001 at 02:22:59PM -0700, Jon Rust wrote: Print the error message to standard output and the server will return this message. This doesn't work with qmail-queue. I have yet to find anyway to get a message either returned to the sending server or to the logs. I've tried printing to standard out and standard error. Can't be done. qmail-smtpd - which calls - qmail-queue - doesn't listen to anything qmail-queue says except it's exit code. To do what you want, you'll have to write your own qmail-queue program that generates a bounce itself - instead of relying on qmail-smtpd to do it. See Qmail-Scanner URL:http://qmail-scanner.sourceforge.net/ for an example. -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
Re: qmail-queue and custom reject message
On Sat, 28 Jul 2001 [EMAIL PROTECTED] wrote: i wrote custom script which substitute qmail-queue, it unpack received message, starting antivirus and if message infected anyone, return code '111' i.e. temporary problem, and deny message relay via server. but, user cannot understand reason of relay-deny. so, server must return custom error message to sender. how i can made it? Print the error message to standard output and the server will return this message.
Re: qmail-queue and custom reject message
On Sat, Jul 28, 2001 at 06:57:33AM -0400, Philip Mak wrote: On Sat, 28 Jul 2001 [EMAIL PROTECTED] wrote: i wrote custom script which substitute qmail-queue, it unpack received message, starting antivirus and if message infected anyone, return code '111' i.e. temporary problem, and deny message relay via server. but, user cannot understand reason of relay-deny. so, server must return custom error message to sender. how i can made it? Print the error message to standard output and the server will return this message. This doesn't work with qmail-queue. I have yet to find anyway to get a message either returned to the sending server or to the logs. I've tried printing to standard out and standard error. jon
Re: qmail-queue and custom reject message
i wrote custom script which substitute qmail-queue, it unpack received message, starting antivirus and if message infected anyone, return Why re-invent the wheel? http://qmail-scanner.sourceforge.net Jeff Palmer [EMAIL PROTECTED]
Re: qmail-queue-patch and qmail-scanner
On Sat, Jul 07, 2001 at 09:19:19PM +0200, Andreas Grip wrote: Well, a smtp-server receiving a lot of mail can reach the limit of maximum allowed simultanius connection. If the smtp server close the connection faster there will be more time over and the server is able to receive more mail. So I think a server, that are faster with closing the connection should be more efficient. If scanning incoming mail takes that long, either upgrade your hardware or push the scanning problem to the end-users (ie. get them to buy an anti-virus package or something). Trying to accept even more mail, when you're already having trouble clearing the mail you've already received, is IMO A Really Bad Idea In A World Full Of Bad Ideas. - Adrian
Re: qmail-queue-patch and qmail-scanner
Charles Cazabon wrote: Andreas Grip [EMAIL PROTECTED] wrote: I don't think this is a great idea; it means you have to accept every message, then scan them, then generate late bounces, instead of rejecting them during the initial SMTP conversation. qmail-scanner do not reject them, it just bounce them. I think you're mistaken, although I don't use qmail-scanner. Issuing a 4xx or 5xx code after DATA _is_ rejecting a message -- it's also a bounce, although if it's done during the SMTP conversation, the sending MTA is responsible for generating the bounce message. Nope, I'm not misstaken. An infected mail is not rejected while my smtp server is receiving the mail, it turn of the connection with an ok. No bounce at this time. And then it sends an bounce to the sender with virus warning message. And what diffrent should that make if the bunce is a few minutes late? It will be late for the sender anyway because they use their ISP:s smtp server and the mail will be sended from that to my smtp server that scan the mail. There's a big difference. See above. Late bounces have to be generated by your MTA and delivered; if the message is bounced during the initial SMTP conversion, the bounce message is the responsibility of the sending MTA, not the receiving one. Maybe there should be an idea to change the behavior of qmail-scanner so it reject the mail instead of accepting it. But then where can not be so much details in the virus report because the sending smtp do not know anything about the virus. What problem are you trying to solve? Why do you think making the SMTP client wait a minute or two is a bad idea? Well, a smtp-server receiving a lot of mail can reach the limit of maximum allowed simultanius connection. If the smtp server close the connection faster there will be more time over and the server is able to receive more mail. So I think a server, that are faster with closing the connection should be more efficient. Profile, don't speculate. You're trying to solve a problem that doesn't exist. I'm not trying to solve a problem that dosen't exist. I'm just trying to make sure that there will not be any problems. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue-patch and qmail-scanner
On Sun, Jul 08, 2001 at 10:57:08AM +0200, Andreas Grip wrote: Nope, I'm not misstaken. An infected mail is not rejected while my smtp server is receiving the mail, it turn of the connection with an ok. No bounce at this time. And then it sends an bounce to the sender with virus warning message. Absolutely right. I cannot send a SMTP error back during the DATA phase otherwise the sending SMTP server just bounces the Email message with little or no reason. SMTP error messages aren't any good when you're wanting to convey an elaborate reason why it bounced (e.g. it was the KAK worm virus) and in several languages :-) OTOH it is still real-time. An original design decisions behind Qmail-Scanner - which I am still happy with - was that I wasn't going to re-invent the wheel and do post-scanning, and I would then have to design my own queuing system, retries, etc. The way it is designed means all such issues are taken care of by standard SMTP. 10-20 minutes is the standard maximum time a SMTP server expects to be sitting in DATA phase, if a mail message takes longer than that to be scanned by whatever virus scanner you have chosen (that will be where the bottleneck is - not with Q-S), then you seriously have to look at: a your choice of scanner b upgrading your hardware. I have seen thrown around the fact that to run a real-time SMTP virus scanner requires around 10x the amount of hardware that not scanning would. Sounds about right. That isn't as bad as it sounds as we all over-spec SMTP relay servers these days anyway. We run two different virus scanners over each piece of Email entering and leaving our network via Qmail-Scanner. The load on these boxes has increased from a load average of 0.02 to 0.06, and climbs to 30+ when we have hour+ network outages. The sudden onslaught of mail after an outage is the killer. Always spec for outages... Also, don't forget, disk IO is most important for SMTP servers. When you start virus scanning, you must add CPU and RAM to that as well. i.e. Big AV mail servers need lots of RAM, lots of CPU as well as fast disks. -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
Re: qmail-queue-patch and qmail-scanner
Andreas Grip [EMAIL PROTECTED] wrote: I'm using the qmail-queue-patch together with the qmail-scanner and I'm also thinking about to put some spamfilters before or after the antivirus scanning. [...] Is it ok to let the sending smtp server to wait so long time before [qmail-scanner] has processed the mail? For me it sounds like a bad idea to let them wait. No, a few minutes wait is perfectly fine. So I'm thinking about to create another queue that the mail can be placed in first so qmail can tell the sender that it has ben received and then start to scan and filtering the mail in that queue before it deliver it to the original queue. I don't think this is a great idea; it means you have to accept every message, then scan them, then generate late bounces, instead of rejecting them during the initial SMTP conversation. What problem are you trying to solve? Why do you think making the SMTP client wait a minute or two is a bad idea? Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue-patch and qmail-scanner
At 12:27 07.07.2001 -0600, you wrote: Andreas Grip [EMAIL PROTECTED] wrote: So I'm thinking about to create another queue that the mail can be placed in first so qmail can tell the sender that it has ben received and then start to scan and filtering the mail in that queue before it deliver it to the original queue. What problem are you trying to solve? Why do you think making the SMTP client wait a minute or two is a bad idea? hmm iam not sure, but what is, if the connected mta thinks that the remote has gone offline, closes the connection and sets the message deferred, and retries later.. getting the same problem again.. iam not if there exist's a such mta, but its possible that this will cause problems like that -- Lukas Maverick Beeler / Telematiker Project: D.R.E.A.M / every.de - Your Community Web: http://www.projectdream.org Mail: [EMAIL PROTECTED]
Re: qmail-queue-patch and qmail-scanner
Lukas Beeler [EMAIL PROTECTED] wrote: At 12:27 07.07.2001 -0600, you wrote: Andreas Grip [EMAIL PROTECTED] wrote: So I'm thinking about to create another queue that the mail can be placed in first so qmail can tell the sender that it has ben received and then start to scan and filtering the mail in that queue before it deliver it to the original queue. What problem are you trying to solve? Why do you think making the SMTP client wait a minute or two is a bad idea? hmm iam not sure, but what is, if the connected mta thinks that the remote has gone offline, closes the connection and sets the message deferred, and retries later.. getting the same problem again.. iam not if there exist's a such mta, but its possible that this will cause problems like that If there's such an MTA, it's broken. RFC2821 states that the absolute minimum timeout the sending MTA can use while waiting for the response to the end of the DATA phase is 10 minutes: DATA Termination: 10 minutes. This is while awaiting the 250 OK reply. When the receiver gets the final period terminating the message data, it typically performs processing to deliver the message to a user mailbox. A spurious timeout at this point would be very wasteful and would typically result in delivery of multiple copies of the message, since it has been successfully sent and the server has accepted responsibility for delivery. See section 6.1 for additional discussion. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue-patch and qmail-scanner
Charles Cazabon wrote: Andreas Grip [EMAIL PROTECTED] wrote: I'm using the qmail-queue-patch together with the qmail-scanner and I'm also thinking about to put some spamfilters before or after the antivirus scanning. [...] Is it ok to let the sending smtp server to wait so long time before [qmail-scanner] has processed the mail? For me it sounds like a bad idea to let them wait. No, a few minutes wait is perfectly fine. So I'm thinking about to create another queue that the mail can be placed in first so qmail can tell the sender that it has ben received and then start to scan and filtering the mail in that queue before it deliver it to the original queue. I don't think this is a great idea; it means you have to accept every message, then scan them, then generate late bounces, instead of rejecting them during the initial SMTP conversation. qmail-scanner do not reject them, it just bounce them. And what diffrent should that make if the bunce is a few minutes late? It will be late for the sender anyway because they use their ISP:s smtp server and the mail will be sended from that to my smtp server that scan the mail. What problem are you trying to solve? Why do you think making the SMTP client wait a minute or two is a bad idea? Well, a smtp-server receiving a lot of mail can reach the limit of maximum allowed simultanius connection. If the smtp server close the connection faster there will be more time over and the server is able to receive more mail. So I think a server, that are faster with closing the connection should be more efficient. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue-patch and qmail-scanner
Andreas Grip [EMAIL PROTECTED] writes: connection faster there will be more time over and the server is able to receive more mail. So I think a server, that are faster with closing the connection should be more efficient. Then the backlog is on your server. You still have to scan the mails and this is the time consuming thing. Additionally you get the overhead of two queues. Regards, Frank
Re: qmail-queue-patch and qmail-scanner
Andreas Grip [EMAIL PROTECTED] wrote: I don't think this is a great idea; it means you have to accept every message, then scan them, then generate late bounces, instead of rejecting them during the initial SMTP conversation. qmail-scanner do not reject them, it just bounce them. I think you're mistaken, although I don't use qmail-scanner. Issuing a 4xx or 5xx code after DATA _is_ rejecting a message -- it's also a bounce, although if it's done during the SMTP conversation, the sending MTA is responsible for generating the bounce message. And what diffrent should that make if the bunce is a few minutes late? It will be late for the sender anyway because they use their ISP:s smtp server and the mail will be sended from that to my smtp server that scan the mail. There's a big difference. See above. Late bounces have to be generated by your MTA and delivered; if the message is bounced during the initial SMTP conversion, the bounce message is the responsibility of the sending MTA, not the receiving one. What problem are you trying to solve? Why do you think making the SMTP client wait a minute or two is a bad idea? Well, a smtp-server receiving a lot of mail can reach the limit of maximum allowed simultanius connection. If the smtp server close the connection faster there will be more time over and the server is able to receive more mail. So I think a server, that are faster with closing the connection should be more efficient. Profile, don't speculate. You're trying to solve a problem that doesn't exist. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail queue
I hope the webmin qmail module wouldn't screw up my config qmail+Vpopmail+Qmailadmin Regards Sumith if all you wanted to do is to look at what is in the queue you could do what I did (although there are probably lots of other solutions that I would be interested in hearing). My solution, as well as the solution to other problems, was to install Webmin 0.84. There is a third-party Qmail module that you could add into it (see www.qmail.org or Webmin.org for more details). This way you can view your local and remote queues seperately over a web browser from anywhere. One note: the Qmail module only partly works right "out of the box". It normally lacks a Perl module that you will need to install seperately in order to view your queues. The Perl module is: TimeDate-1.10 hope this helps. -G -Original Message- From: Sumith To: Qmail Sent: 3/22/01 11:03 PM Subject: qmail queue Hello All Excuse me if this question has been repeated a lot of times... I've install qmail from memphis rpms. also VPOPMAIL 4.9.8-1 How can I know how many concurrent qmail deliveries are taking place on my qmail server, both qmail-local and qmail-remote I have applied the qmail-concurrent-patch, and big-todo-patch There is no concurrencylocal and concurrencyremote presently in /var/qmail/control If the default is 10 for concurrencylocal and 20 for concurrency remote (which lwq says)what would be the safe number to increase this to on my PIII 800 , 512 MB RAM, IDE hard disk handling about 500 virtual domains. I hope that some one helps me to clear my doubts. Regards Sumith
Re: qmail queue
Sumith [EMAIL PROTECTED] wrote: How can I know how many concurrent qmail deliveries are taking place on my qmail server, both qmail-local and qmail-remote qmail's logs include this information in the "status:" lines. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: qmail queue
"Sumith" [EMAIL PROTECTED] wrote: How can I know how many concurrent qmail deliveries are taking place on my qmail server, both qmail-local and qmail-remote Look at your qmail-send logs. You should see something like: @40003abb67f02a8b74e4 status: local 0/60 remote 14/500 where concurrencylocal is 60 and concurrencyremote is 500. -Dave
RE: qmail queue
Sumith, if all you wanted to do is to look at what is in the queue you could do what I did (although there are probably lots of other solutions that I would be interested in hearing). My solution, as well as the solution to other problems, was to install Webmin 0.84. There is a third-party Qmail module that you could add into it (see www.qmail.org or Webmin.org for more details). This way you can view your local and remote queues seperately over a web browser from anywhere. One note: the Qmail module only partly works right "out of the box". It normally lacks a Perl module that you will need to install seperately in order to view your queues. The Perl module is: TimeDate-1.10 hope this helps. -G -Original Message- From: Sumith To: Qmail Sent: 3/22/01 11:03 PM Subject: qmail queue Hello All Excuse me if this question has been repeated a lot of times... I've install qmail from memphis rpms. also VPOPMAIL 4.9.8-1 How can I know how many concurrent qmail deliveries are taking place on my qmail server, both qmail-local and qmail-remote I have applied the qmail-concurrent-patch, and big-todo-patch There is no concurrencylocal and concurrencyremote presently in /var/qmail/control If the default is 10 for concurrencylocal and 20 for concurrency remote (which lwq says)what would be the safe number to increase this to on my PIII 800 , 512 MB RAM, IDE hard disk handling about 500 virtual domains. I hope that some one helps me to clear my doubts. Regards Sumith
Re: qmail queue
-Original Message- From: Sumith To: Qmail Sent: 3/22/01 11:03 PM Subject: qmail queue How can I know how many concurrent qmail deliveries are taking place on my qmail server, both qmail-local and qmail-remote Regards Sumith Call me old fashioned, but when I want to see what my qmail server is doing I just do a: ps auxw | grep qmail or, if I just want to see outbound mail from external users: ps auxw | grep qmail-remote `qmail-qstat` is also a somewhat useful command to get a general idea on your mail server's current load. -- Keith Network Engineer Triton Technologies, Inc.
RE: Qmail Queue is out of control ....
The thing is, that mails are stuck in the queue and I want to make them go
...
I've tried kill -ALRM qmail-send without succes :((
And now, I'm still stuck and I become crazy #:{{
-Message d'origine-
De : Charles Cazabon [mailto:[EMAIL PROTECTED]]
Envoy : vendredi 2 mars 2001 16:38
: Qmail
Objet : Re: Qmail Queue is out of control
Frdric Belteau [EMAIL PROTECTED] wrote:
I seems as if I have a problem with my qmail queue. A lots of mails are
stuck in it and I do not know how to send them.
Having messages in the queue isn't a problem -- that's what a queue is for.
Why do you think it's a problem? It's probably just mail to servers which
are
slow or down or poorly connected.
Show us the log entries which make you think that the messages in your
queue are a problem.
Charles
--
---
Charles Cazabon[EMAIL PROTECTED]
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
---
Re: Qmail Queue is out of control ....
Frdric Belteau [EMAIL PROTECTED] wrote:
The thing is, that mails are stuck in the queue and I want to make them go
...
I've tried kill -ALRM qmail-send without succes :((
And now, I'm still stuck and I become crazy #:{{
If they're "stuck" in the queue, there's a reason for it. That reason will
be clearly indicated in the qmail logs. Post a section of the qmail log
detailing why one of these messages is not being succesfully delivered.
Chances are there's nothing you can do about it, as its probably just a
non-responsive server.
Why does having mail sit in your queue bother you, anyway? It's a fact of
life for internet mail. Get used to it.
Charles
--
---
Charles Cazabon[EMAIL PROTECTED]
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
---
RE: Qmail Queue is out of control ....
My log file looks like this :
984126108.972553 warning: trouble opening remote/19/66328; will try again
later
Right now, I have 12536 lines in it !!
-Message d'origine-
De : Charles Cazabon [mailto:[EMAIL PROTECTED]]
Envoy : vendredi 9 mars 2001 15:19
: Qmail
Objet : Re: Qmail Queue is out of control
Frdric Belteau [EMAIL PROTECTED] wrote:
The thing is, that mails are stuck in the queue and I want to make them go
...
I've tried kill -ALRM qmail-send without succes :((
And now, I'm still stuck and I become crazy #:{{
If they're "stuck" in the queue, there's a reason for it. That reason will
be clearly indicated in the qmail logs. Post a section of the qmail log
detailing why one of these messages is not being succesfully delivered.
Chances are there's nothing you can do about it, as its probably just a
non-responsive server.
Why does having mail sit in your queue bother you, anyway? It's a fact of
life for internet mail. Get used to it.
Charles
--
---
Charles Cazabon[EMAIL PROTECTED]
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
---
Re: Qmail Queue is out of control ....
Frdric Belteau [EMAIL PROTECTED] wrote: My log file looks like this : 984126108.972553 warning: trouble opening remote/19/66328; will try again later Ah, this is different -- this isn't just messages sitting in the queue, this is queue corruption. Did you try deleting files out of /var/qmail/queue manually? Solution: download queue-fix from qmail.org and compile it. Stop qmail. Run queue-fix with appropriate arguments. Make sure it reports all errors are fixed. Restart qmail. And never modify the queue while qmail is running, ever. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
RE: Qmail Queue is out of control ....
I've just tried to fix je queu with queue-fix and It made nothing more :(( Is their another solution ? -Message d'origine- De : Charles Cazabon [mailto:[EMAIL PROTECTED]] Envoy : vendredi 9 mars 2001 15:35 : Qmail Objet : Re: Qmail Queue is out of control Frdric Belteau [EMAIL PROTECTED] wrote: My log file looks like this : 984126108.972553 warning: trouble opening remote/19/66328; will try again later Ah, this is different -- this isn't just messages sitting in the queue, this is queue corruption. Did you try deleting files out of /var/qmail/queue manually? Solution: download queue-fix from qmail.org and compile it. Stop qmail. Run queue-fix with appropriate arguments. Make sure it reports all errors are fixed. Restart qmail. And never modify the queue while qmail is running, ever. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Qmail Queue is out of control ....
Frdric Belteau [EMAIL PROTECTED] wrote: I've just tried to fix je queu with queue-fix and It made nothing more :(( I don't quite follow this. However... Is their another solution ? Yes: -stop qmail `rm -rf /var/qmail/queue` -cd into the qmail source directory `make setup check` -restart qmail Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Qmail Queue is out of control ....
Please note this will destroy the contents of your queue. This message is to prevent any future messages from this person blaming the list members for his messages disappearing. Sean - Original Message - From: "Charles Cazabon" [EMAIL PROTECTED] To: "Qmail" [EMAIL PROTECTED] Sent: Friday, March 09, 2001 9:41 AM Subject: Re: Qmail Queue is out of control Frdric Belteau [EMAIL PROTECTED] wrote: I've just tried to fix je queu with queue-fix and It made nothing more :(( I don't quite follow this. However... Is their another solution ? Yes: -stop qmail `rm -rf /var/qmail/queue` -cd into the qmail source directory `make setup check` -restart qmail Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Qmail Queue is out of control ....
Frdric Belteau [EMAIL PROTECTED] wrote: I seems as if I have a problem with my qmail queue. A lots of mails are stuck in it and I do not know how to send them. Having messages in the queue isn't a problem -- that's what a queue is for. Why do you think it's a problem? It's probably just mail to servers which are slow or down or poorly connected. Show us the log entries which make you think that the messages in your queue are a problem. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: QMAIL- QUEUE FILE SYSTEM FULL
qmailu [EMAIL PROTECTED] wrote: I have setup qmail with 3.5 lac users and my filesystem which contains qmail,vpopmail and hence the queue has become full. How can i move the qmail-queue to a different file system (I already have another file system with plenty of disk space. I currently have 15000 mails in queue. I want to clear my queue right away without having to wait for the queue to clear by themselves. Is there a way to start clearing this queue. 1. Mount your new filesystem at /var/qmail2 2. Configure and install a new instance of qmail, under /var/qmail2 3. Stop qmail-smtpd from your original qmail install, and start the qmail-smtpd from qmail2, so new messages go into /var/qmail2/queue 4. Disable/remove qmail-inject, mailsubj, etc which are currently injecting into the old queue. Make everyone use the newly-installed ones, which are injecting into the new queue in /var/qmail2/queue 5. Wait a week for the remainder of messages in the old queue to either be delivered or bounced. 6. Remove the old /var/qmail installation completely. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: qmail queue problems .. help
Jos Carreiro [EMAIL PROTECTED] wrote: i'm wondering if exists some binaries or scripts to cleanup/fix the qmail queue Read www.qmail.org. There's several links there that do precisely this. i'm also receiving messages from foreign hosts about outgoing messages bouncing from my server ... You'll need to be more descriptive for us to help you with this. Try actually posting the messages you're receiving, for a start. You should also tell us the hostname of your mailserver, as many common problems can be diagnosed with a simple DNS query and possibly telnetting to your SMTP port. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: qmail queue problems .. help
i'm wondering if exists some binaries or scripts to cleanup/fix
the qmail queue
( /opt/qmail/queue/mess
/remote
/info
/bounce)
Have a look at:
http://www.faqts.com/knowledge_base/view.phtml/aid/1217/fid/206 :
--
How can I delete a lot of spam mail from the qmail queue?
May 9th, 2000 06:35
Howard Jones, Nathan Wallace
Magnus Bodin
Take a look at qmhandle:
http://www.io.com/~mick/soft/qmhandle.html
Don't forget to stop qmail before you mess around in the queue.
An alternative that I've used successfully is to
1) Stop qmail, qmail-smtpd and anything else that might try to deliver
messages - leave qmail-pop3d, then at least users can get their
existing mail.
2) Delete the offending messages from the /var/qmail/queue/mess
directories with something like:
find /var/qmail/queue/mess -type f -exec grep "^Subject: Want a
University Diploma" {} \; -print -exec rm {} \;
3) run queue-fix to clean up the appropriate related files in todo,
intd etc.
4) restart qmail.
qmhandle requires individual message numbers to delete messages. When
you have 100,000 messages, this is impractical! queue-fix is written by
Eric Huss, and is available at
http://www.netmeridian.com/e-huss/queue-fix.tar.gz
It's also worth knowing that the find command will still potentially
take hours to delete all that junk - be prepared for some phonecalls!
--
cya
Joel
Re: qmail-queue
Am 20.01.2001 um 22:05:42 schrieb NDSoftware: Hi, Hi Nicolas, Can you send me a qmail-queue patched for use with qmail-scanner, why don't we try to get it to run on your computer? It might not be a good idea to take a program from someone you do not know, sent to you per mail. You can imagine yourself what could happen. because i have patched qmail-queue how did you do this? where did you download the patch? how did you call patch (commandline). What did patch say? but the 2 files have the same size ! this is not necesarily a problem but very likely patch failed. Have a look at the patched file and try to find the lines in the patch file. Are they there? regards /ch
Re: QMail Queue
"NDSoftware" [EMAIL PROTECTED] wrote: Where i can get log for QMail Queue because i have '451 qq Temporary Problem (#4.3.0)' when in send a mail after install AVP. How did you configure your logging? -Dave
Re: qmail-queue patch
It's officailly documented as this : root:/usr/local/src/qmail-1.03# patch -p1 /path/to/qmail-103.patch from the qmail-howto. But this command did not work for me, who knows, maybe I did something wrong. regards chris
Re: qmail-queue patch
* lkhanna [EMAIL PROTECTED] writes: can anybody tell me how can i apply qmail-queue patch on existing running qmail-1.03, qmail patch ois available on qmail.org site but i don't know how to aply that , bcoz its neither a tar file nor a rpm, So could u pl help me in applying that u nd t rd th fckng mn pg fr ptch nd ptch th qml srcs, rcmpl, stp qml nd rnstll. And IYAM, this shorthand thingy is kind hrd t rd. -- Robin S. Socha http://socha.net/
Re: qmail-queue patch
"Robin" == Robin S Socha [EMAIL PROTECTED] writes: Robin u nd t rd th fckng mn pg fr ptch nd ptch th qml srcs, rcmpl, Robin stp qml nd rnstll. And IYAM, this shorthand thingy is kind hrd Robin t rd. "f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng." - Anonymous, 19alongtimeago Sorry, couldn't resist that quote. -- "BUG, n.: An undesirable, poorly-understood undocumented feature." - The Devil's Dictionary to Computer Studies
Re: qmail queue
how do we properly clear the queue? right now i have about 98,000 messages in queue and this is hanging qmail. please help, this is rather urgent Sonam Wangchuk e: [EMAIL PROTECTED]
Re: qmail queue
On Wed, Sep 06, 2000 at 01:50:26PM -0400, [EMAIL PROTECTED] wrote: how do we properly clear the queue? right now i have about 98,000 messages in queue and this is hanging qmail. please help, this is rather urgent what do you want to do ? expire the messages (- 98'000 error messages),or simply delete everything ? Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
actually delete everything in queue. i found out about qmHandle but due to so many messages, its taking a long time to even do a listing. i might as well delete all the mails in queue manually. thanks Sonam Wangchuk e: [EMAIL PROTECTED] On Wed, 6 Sep 2000, Olivier M. wrote: On Wed, Sep 06, 2000 at 01:50:26PM -0400, [EMAIL PROTECTED] wrote: how do we properly clear the queue? right now i have about 98,000 messages in queue and this is hanging qmail. please help, this is rather urgent what do you want to do ? expire the messages (- 98'000 error messages),or simply delete everything ? Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
On Wed, Sep 06, 2000 at 02:30:55PM -0400, [EMAIL PROTECTED] wrote: actually delete everything in queue. i found out about qmHandle but due to so many messages, its taking a long time to even do a listing. i might as well delete all the mails in queue manually. thanks well, what about stoping qmail, rm /var/qmail/queue/mess/* rm /var/qmail/queue/info/* rm /var/qmail/queue/local/* rm /var/qmail/queue/remote/* and starting qmail again ? Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
[EMAIL PROTECTED] wrote: how do we properly clear the queue? That depends on the nature of the messages in the queue. If they're all spam, you can stop qmail, remove them, and restart qmail. If they're valid messages that need to be delivered, qmail will deliver them ASAP and clear them automatically. You can increase concurrencylocal and/or concurrencyremote to speed things up, and you can shorten queuelifetime to bounce undeliverable messages faster. right now i have about 98,000 messages in queue and this is hanging qmail. Hanging? What do you mean? Do you have log evidence to back up this claim? -Dave
Re: qmail queue
there is one more directory in /var/qmail/queue called todo, should we remove that too? what is that directory? thank you for your quick response. Sonam Wangchuk e: [EMAIL PROTECTED] On Wed, 6 Sep 2000, Olivier M. wrote: On Wed, Sep 06, 2000 at 02:30:55PM -0400, [EMAIL PROTECTED] wrote: actually delete everything in queue. i found out about qmHandle but due to so many messages, its taking a long time to even do a listing. i might as well delete all the mails in queue manually. thanks well, what about stoping qmail, rm /var/qmail/queue/mess/* rm /var/qmail/queue/info/* rm /var/qmail/queue/local/* rm /var/qmail/queue/remote/* and starting qmail again ? Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
On Wed, Sep 06, 2000 at 08:48:13PM +0200, Olivier M. wrote: On Wed, Sep 06, 2000 at 02:30:55PM -0400, [EMAIL PROTECTED] wrote: actually delete everything in queue. i found out about qmHandle but due to so many messages, its taking a long time to even do a listing. i might as well delete all the mails in queue manually. thanks well, what about stoping qmail, rm /var/qmail/queue/mess/* rm /var/qmail/queue/info/* rm /var/qmail/queue/local/* rm /var/qmail/queue/remote/* Actually, that wont work, there are directories at this level, you need to go one level lower. rm /var/qmail/queue/remote/*/* etc. You also need to include todo and bounce. Or alternatively, # cd /var/qmail/queue # find bounce todo mess info local remote -type f -print | xargs rm Alternative number two (my preferred as directories grow without shrinking on many OSes and rm of files doesn't fix that): # mv /var/qmail/queue /var/qmail/queue.old # rm -rf /var/qmail/queue.old # cd /qmail-1.03 # make setup Regards.
Re: qmail queue
after removing all the files as mentioned, when i try to send email i get "qmail-inject: fatal: qq trouble creating files in queue (#4.3.0)" why is this error coming up? before removing all the file i did try to move the todo directory on another file system and created a link from /var/qmail/queue/todo, and started qmail at which time i got this same error. so i sent the email to your mailing list asking for help in removing the mails in queue. i did create the todo directory in /var/qmail/queue/ with the correct permissions. Sonam Wangchuk e: [EMAIL PROTECTED] On Wed, 6 Sep 2000, Olivier M. wrote: On Wed, Sep 06, 2000 at 02:30:55PM -0400, [EMAIL PROTECTED] wrote: actually delete everything in queue. i found out about qmHandle but due to so many messages, its taking a long time to even do a listing. i might as well delete all the mails in queue manually. thanks well, what about stoping qmail, rm /var/qmail/queue/mess/* rm /var/qmail/queue/info/* rm /var/qmail/queue/local/* rm /var/qmail/queue/remote/* and starting qmail again ? Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
On Wed, Sep 06, 2000 at 02:50:39PM -0400, [EMAIL PROTECTED] wrote: there is one more directory in /var/qmail/queue called todo, should we remove that too? what is that directory? thank you for your quick response. well, it's empty on my servers, so I think you can also empty them... Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
actually these are mails that are no longer needed, so that's why i can remove them. i can not send any mail and it seems to be because all these messages in queue. i stopped and restarted qmail. i even rebooted the box. that's why i used "hanging". but right now i am getting this error message qmail-inject: fatal: qq trouble creating files in queue (#4.3.0) which i have explained in my previous email to the mailing list. thank you all for your quick response. Sonam Wangchuk e: [EMAIL PROTECTED] On Wed, 6 Sep 2000, Dave Sill wrote: [EMAIL PROTECTED] wrote: how do we properly clear the queue? That depends on the nature of the messages in the queue. If they're all spam, you can stop qmail, remove them, and restart qmail. If they're valid messages that need to be delivered, qmail will deliver them ASAP and clear them automatically. You can increase concurrencylocal and/or concurrencyremote to speed things up, and you can shorten queuelifetime to bounce undeliverable messages faster. right now i have about 98,000 messages in queue and this is hanging qmail. Hanging? What do you mean? Do you have log evidence to back up this claim? -Dave
Re: qmail queue
On Wed, Sep 06, 2000 at 03:55:34PM -0400, [EMAIL PROTECTED] wrote: after removing all the files as mentioned, when i try to send email i get "qmail-inject: fatal: qq trouble creating files in queue (#4.3.0)" why is this error coming up? mmm the best would be to remove (or move) completely the queue directory, and do a "make setup" in the qmail source tree : I had to do that on an old server to make qmail start again. (btw, this stuff should come in the FAQ, don't you think so ?) Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
Re: qmail queue
On Wed, Sep 06, 2000 at 03:55:34PM -0400, [EMAIL PROTECTED] wrote: after removing all the files as mentioned, when i try to send email i get "qmail-inject: fatal: qq trouble creating files in queue (#4.3.0)" It sounds like you removed more than was suggested. You have now broken your queue because you did not read the reply to your question carefully. why is this error coming up? before removing all the file i did try to move the todo directory on another file system and created a link from /var/qmail/queue/todo, and It sounds like you removed *and moved* more than was suggested. You have now *really* broken your queue because you did not read the replies to your question carefully. Did someone suggest that you create todo on another file system and do what you did? Or did you somehow extrapolate from the answers people posted here? In any event it is very wrong. Do my preferred alternative as posted earlier. If you no longer have that email, it'll be in the archives for this list. Regards.
Re: qmail queue
thank you to all. i have removed the queue and started qmail. thank you again. Sonam Wangchuk e: [EMAIL PROTECTED] On Wed, 6 Sep 2000 [EMAIL PROTECTED] wrote: On Wed, Sep 06, 2000 at 08:48:13PM +0200, Olivier M. wrote: On Wed, Sep 06, 2000 at 02:30:55PM -0400, [EMAIL PROTECTED] wrote: actually delete everything in queue. i found out about qmHandle but due to so many messages, its taking a long time to even do a listing. i might as well delete all the mails in queue manually. thanks well, what about stoping qmail, rm /var/qmail/queue/mess/* rm /var/qmail/queue/info/* rm /var/qmail/queue/local/* rm /var/qmail/queue/remote/* Actually, that wont work, there are directories at this level, you need to go one level lower. rm /var/qmail/queue/remote/*/* etc. You also need to include todo and bounce. Or alternatively, # cd /var/qmail/queue # find bounce todo mess info local remote -type f -print | xargs rm Alternative number two (my preferred as directories grow without shrinking on many OSes and rm of files doesn't fix that): # mv /var/qmail/queue /var/qmail/queue.old # rm -rf /var/qmail/queue.old # cd /qmail-1.03 # make setup Regards.
Re: qmail-queue wrapper (like qmail-qfilter)
On Wed, 30 Aug 2000, Ricardo Albano wrote:
Any had implemented qmail-qfilter sucefully or any qmail-queue wrapper ?
RDA.-
I have a generic qmail-queue-wrapper program. It's written in perl and
in its standard form, does nothing but add another Received header to
the message before calling the real qmail-queue. If you can program in
perl you can get it to do whatever you want. I'm using it to do header
rewrites at one site.
It should be installed with no special permissions
-rwx--x--x qmailq qmail /var/qmail/bin/qmail-queue
Program is attached.
You can also have a look at Jason Haar's scan4virus program. It too is
a perl qmail-queue-wrapper. Details at www.qmail.org.
--
Regards
Peter
--
Peter Samuel[EMAIL PROTECTED]
http://www.e-smith.org (development)http://www.e-smith.com (corporate)
Phone: +1 613 368 4398 Fax: +1 613 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
"If you kill all your unhappy customers, you'll only have happy ones left"
#!/pkgs/bin/perl -w
#
# $Id: qmail-queue-wrapper.pl,v 1.1 2000/05/31 07:20:37 psamuel Exp $
#
# qmail-queue wrapper program.
#
# This program should be used when you wish to manipulate a mail
# message BEFORE it is placed in the queue. Possible uses include:
#
#- header rewriting
#- Firstname.Lastname replacements
#- virus scanning
#- anything else you can think of
#
# There are at least 2 ways of using this program:
#
#1) Replace the original qmail-queue with this program:
#
# mv /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig
# cp qmail-queue-wrapper /var/qmail/bin/qmail-queue
#
#Change the value of $qmailqueue below, to reflect the new name of
#the original qmail-queue program. For example
#
# my $qmailqueue = "/var/qmail/bin/qmail-queue.orig";
#
#2) Recompile qmail with Bruce Guenter's QMAILQUEUE patch. (See
#http://www.qmail.org/qmailqueue-patch). Then any program that
#needs to use this program can be called with the environment
#variable QMAILQUEUE set to /var/qmail/bin/qmail-queue-wrapper
#
# How does it work? The interface to the real qmail-queue is simple:
#
# - the body of the message is read from file descriptor 0
# - the envelope details are read from file descriptor 1.
#
# qmail-queue-wrapper also adheres to the same interface. After doing
# whatever manipulations are necessary, it calls the real qmail-queue
# and provides the message body on file descriptor 0 and the envelope
# details on file descriptor 1.
#
# Exit codes conform to those mentioned in the qmail-queue(8) manual page.
#
###
require 5;
use strict;
my $child;
my $debug = 0;
my $envelope;
my %errors;
my @months;
my $new_received_header;
my $qmailqueue = "/var/qmail/bin/qmail-queue.orig";
my @recipients;
my $sender;
###
initialise();
if ($child = fork())
{
# Parent
my $timeout = 86400;# See qmail-queue.c, line 20
alarm($timeout);
fatal(82) unless close MESSAGE_READER;
fatal(82) unless close ENVELOPE_READER;
process_message();
process_envelope();
# Wait for the child to terminate
waitpid($child, 0);
# Return with the exit status of the child
exit($? % 255);
}
elsif (defined $child)
{
# Child
fatal(82) unless close MESSAGE_WRITER;
fatal(82) unless close ENVELOPE_WRITER;
fatal(82) unless defined open(STDIN, "MESSAGE_READER");
fatal(82) unless defined open(STDOUT, "ENVELOPE_READER");
if ($debug)
{
debug_message("$$: Reading message from STDIN\n\n");
while (STDIN)
{
debug_message("$$: $_");
}
fatal(82) unless close MESSAGE_READER;
debug_message("\n$$: \n\n");
debug_message("$$: Reading envelope from STDOUT\n");
while (ENVELOPE_READER)
{
s/\0/ /g;
debug_message("$$: $_\n");
}
fatal(82) unless close ENVELOPE_READER;
exit(0);
}
else
{
unless (exec $qmailqueue)
{
# We shouldn't be here unless the exec failed
fatal(82);
}
}
}
else
{
# Unable to fork
fatal(82);
}
###
sub initialise
{
prepare_months();
prepare_error_messages();
ignore_signals();
catch_signals();
generate_new_received_header();
setup_pipes();
}
sub prepare_months
{
@months = (
"Jan", "Feb", "Mar", "Apr",
"May", "Jun", "Jul", "Aug",
"Sep", "Oct", "Nov", "Dec",
);
}
sub prepare_error_messages
{
Re: qmail-queue, URGENT!
Jorge Rocha [EMAIL PROTECTED] wrote: May 16 16:21:05 lx1 qmail: 958504865.479739 delivery 38: deferral: Connected_to_200.246.122.250_but_connection_died._Possible_duplicate!_(#4.4.2)/ After 3 days the message is bounced, but i already checked the remote server and there are no error! Anybody knows what going on? 200.246.122.250 is closing the SMTP connection to your qmail before acknowledging the receipt of the message. Under these conditions, qmail has to assume that the message didn't go through. This is a violation of SMTP. Which MTA is 200.246.122.250 running? -Dave
Re: qmail-queue, URGENT!
On Tue, May 16, 2000 at 03:54:32PM -0400, Dave Sill wrote: [snip] 200.246.122.250 is closing the SMTP connection to your qmail before acknowledging the receipt of the message. Under these conditions, qmail has to assume that the message didn't go through. This is a violation of SMTP. Which MTA is 200.246.122.250 running? After a few tries, it reports No route to host. The box in question is also the secondary MX for node1.com.br. Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
Re: qmail-queue was killed?
+ Fred backman [EMAIL PROTECTED]: | My mail server has been working okay until recently, and I cannot | figure out why it's not working. This is what I get when I try to | send a message locally: | | # echo bollox | /var/qmail/bin/qmail-inject | qmail-inject: fatal: qmail-queue was killed | | Nothing shows up in the syslog. Nothing in the mail queue. | | Sending to the "bollox" account via smtp works just fine! Any ideas? As a first try, you could try to present a valid message to qmail-inject: # echo to: bollox | /var/qmail/bin/qmail-inject If it still fails, turn on process tracing (if your system allows it) and see what happens to the process. - Harald
Re: qmail-queue was killed?
- Original Message - As a first try, you could try to present a valid message to qmail-inject: # echo to: bollox | /var/qmail/bin/qmail-inject Sorry, that was a typo. I did exactly the line you suggested. If it still fails, turn on process tracing (if your system allows it) and see what happens to the process. Do you mean I should trace qmail-queue? If so, how do I do that when qmail-queue is invoked from qmail-inject? I tried tracing qmail-inject but I couldn't figure out why qmail-queue was killed. Here's the tail of the trace. Any further ideas? # echo to: bollox | truss /var/qmail/bin/qmail-inject junk # tail junk close(4)= 0 write(6, " F r o o t @ c r a p .".., 67) = 67 write(6, "\0", 1) = 1 close(6)= 0 Received signal #18, SIGCLD, in wait() [default] siginfo: SIGCLD CLD_KILLED pid=2415 status=0x000B wait() = 2415 [0x000B] qmail-inject: fatal: qmail-queue was killed write(2, " q m a i l - i n j e c t".., 44) = 44 _exit(111)
Re: qmail-queue was killed?
+ "Fred Backman" [EMAIL PROTECTED]: | If it still fails, turn on process tracing (if your system allows it) | and see what happens to the process. | | Do you mean I should trace qmail-queue? If so, how do I do that when | qmail-queue is invoked from qmail-inject? You seem to be on a Solaris system. Then use truss -f to trace the children. (You can also use -o filename to redirect the trace output.) Since qmail-queue is a setuid program you have to be root to do this, but then I believe it will work. - Harald
Re: qmail-queue was killed?
- Original Message -
From: Harald Hanche-Olsen [EMAIL PROTECTED]
| Do you mean I should trace qmail-queue? If so, how do I do that when
| qmail-queue is invoked from qmail-inject?
You seem to be on a Solaris system. Then use truss -f to trace the
children. (You can also use -o filename to redirect the trace
output.) Since qmail-queue is a setuid program you have to be root to
do this, but then I believe it will work.
Thanks for the advice, Harald! Ok, here's what I get now using -f flag:
(first what seems to be "normal" trace output, and then around line 100)
2761: close(6)= 0
2761: fcntl(3, F_GETFL, 0x) = 2
2761: ioctl(3, I_FIND, "sockmod") = 0
2761: close(0)= 0
2761: fcntl(3, F_DUPFD, 0x) = 0
2761: close(3)= 0
2761: fcntl(5, F_GETFL, 0x) = 2
2761: ioctl(5, I_FIND, "sockmod") = 0
2761: close(1)= 0
2761: fcntl(5, F_DUPFD, 0x0001) = 1
2761: close(5)= 0
2761: execve("bin/qmail-queue", 0x0002F1DC, 0xE91C) argc = 1
2761: *** SUID: ruid/euid/suid = 0 / 1129 / 1129 ***
2761: open("/dev/zero", O_RDONLY) Err#13 EACCES
2761: open("/dev/zero", O_RDONLY) Err#13 EACCES
...
(*thousands* of these EACCES error messages, and then the tail)
...
2761: open("/dev/zero", O_RDONLY) Err#13 EACCES
2761: Incurred fault #6, FLTBOUNDS %pc = 0xEF7E6D8C
2761: siginfo: SIGSEGV SEGV_MAPERR addr=0xEF7FFFE8
2761: Received signal #11, SIGSEGV [default]
2761: siginfo: SIGSEGV SEGV_MAPERR addr=0xEF7FFFE8
2760: Received signal #18, SIGCLD, in wait() [default]
2760: siginfo: SIGCLD CLD_KILLED pid=2761 status=0x000B
2760: wait() = 2761 [0x000B]
qmail-inject: fatal: qmail-queue was killed
2760: write(2, " q m a i l - i n j e c t".., 44) = 44
2760: _exit(111)
2761: *** process killed ***
Re: qmail-queue was killed?
On 30-Sep-99 Fred Backman wrote:
2761: open("/dev/zero", O_RDONLY) Err#13 EACCES
2761: open("/dev/zero", O_RDONLY) Err#13 EACCES
...
Check the privileges on /devices/pseudo/mm@0:zero, they should be
something like:
crw-rw-rw- 1 root sys 13, 12 Oct 23 1998 /devices/pseudo/mm@0:zero
Stefaan
--
PGP key available from PGP key servers (http://www.pgp.net/pgpnet/)
___
In a world where everyone uses an alias, one's real identity is
the best disguise.
Fixed it -- thanks!! (Re: qmail-queue was killed?)
Just for the record: The problem with "qmail-queue was killed" turned out to be bogus permission mode on the root directory (which somehow affected qmail-queue's access to /dev/zero). # ls -ld / drwx---r-x 35 root root1536 Sep 4 08:47 // should obviously have been drwxr-xr-x 35 root root1536 Sep 4 08:47 // Extra special thanks to Harald Hanche-Olsen for helping me! :-) cheers Fred
Re: qmail queue
Eric Dahnke [EMAIL PROTECTED] wrote: qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. In reference to this, I thought descriptor 0 was STDIN and descriptor 1 was STDOUT, How can qmail-queue read envelop information from descriptor 1. qmail-queue doesn't use stdin/stdout/stderr, so those descriptors are available for other uses. -Dave
Re: qmail queue
So how does the message pass between the various parts of the qmail structure (inject, queue, send), if not via STDIN and OUT? I want to write a wrapper for qmail-queue, but am a novice. This is a long term project. thx Dave Sill escribió: Eric Dahnke [EMAIL PROTECTED] wrote: qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. In reference to this, I thought descriptor 0 was STDIN and descriptor 1 was STDOUT, How can qmail-queue read envelop information from descriptor 1. qmail-queue doesn't use stdin/stdout/stderr, so those descriptors are available for other uses. -Dave
Re: qmail queue
At 02:22 PM Monday 9/13/99, Eric Dahnke wrote: So how does the message pass between the various parts of the qmail structure (inject, queue, send), if not via STDIN and OUT? I want to write a wrapper for qmail-queue, but am a novice. This is a long term project. thx Eric. These are more "How do I use Unix file descriptor" questions rather than "How do I use qmail" questions. If this sort of thing is new to you, which your question suggests, a good place to start would be a book or discussion forum on how to program on a Unix platform. Whilst many people on this list are expert at Unix, it's probably not the most appropriate forum for a novice discussion on file descriptor usage on Unix. Regards. Dave Sill escribió: Eric Dahnke [EMAIL PROTECTED] wrote: qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. In reference to this, I thought descriptor 0 was STDIN and descriptor 1 was STDOUT, How can qmail-queue read envelop information from descriptor 1. qmail-queue doesn't use stdin/stdout/stderr, so those descriptors are available for other uses. -Dave
Re: qmail queue
Eric Dahnke writes: DESCRIPTION qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. In reference to this, I thought descriptor 0 was STDIN and descriptor 1 was STDOUT, How can qmail-queue read envelop information from descriptor 1. The shell imposes the concept of stdin, stdout, and stderr. Other than that, you're free to use any uid for anything you want. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Government schools are so 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Re: Qmail-queue wrapper (spam filter)
Ben Heilman writes: Hello all, I have been trying to write a SPAM filter which is a wrapper for qmail-queue, so that it may act on information in the actual email message. Unfortunately, my C skills are not the best. I realize that qmail-smtpd will first feed the email via file desciptor 0 to qmail-queue, then feed the envelop info via file desciptor 1 and terminate with \0\0. However, I do not wish to pull all this feed into memory. (25M messages would be a system killer) I have tried and tried, but the method escapes me. If anyone has some sample code for a wrapper and is willing the share it, I would much appreciate it. I've been working on one for a customer. Give me a few days to work out the particulars of distribution. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Government schools are so 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Re: Qmail::Queue
On Sun, Jul 25, 1999 at 11:02:53PM -0700, Russ Allbery wrote: Russell Nelson [EMAIL PROTECTED] writes: Anybody written a Perl module for Qmail::Queue? For talking to qmail-queue? Not quite, but it would be almost trivial to turn my mjinject code into one. As someone who's looked at the code, I second that comment. -- John White johnjohn at triceratops.com PGP Public Key: http://www.triceratops.com/john/public-key.pgp
Re: Qmail::Queue
Russell Nelson [EMAIL PROTECTED] writes: Anybody written a Perl module for Qmail::Queue? For talking to qmail-queue? Not quite, but it would be almost trivial to turn my mjinject code into one. -- Russ Allbery ([EMAIL PROTECTED]) URL:http://www.eyrie.org/~eagle/
Re: qmail queue + perl question
Wilson Fletcher [EMAIL PROTECTED] wrote:
The FAQ says this:
7.3. How do I rejuvenate a message? Somebody broke into Eric's computer
... I see it sitting here
in /var/qmail/queue/mess/15/26902...
Answer: Just touch /var/qmail/queue/info/15/26902. (This is the only
form of queue modification that's safe while qmail is running.)
BUT it doesn't give any indication of how the author actually knew that
/var/qmail/queue/info/15/26902 was the message in question or how he/she
knew to look in .../queue/info/15/ for it.
find /var/qmail/queue -type f -exec grep "some unique string" {} /dev/null \;
Will search the queue for "some unique string" (could be a message-id
or eric's e-mail address). That'll give you the message number (the
26902 part) as well as the split directory (the 15 part).
-Dave
Re: qmail queue + perl question
On Jun 01 1999, Wilson Fletcher wrote: The FAQ says this: 7.3. How do I rejuvenate a message? Somebody broke into Eric's computer ^ ^^ (...) Haha! Anytime I read the FAQ I ROTFL, man! And I keep seeing people complaining about the documentation on qmail not being appropriate... :-) Really, how could it be any better? :-) You even have a good time reading it... :-) []s, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ (still an) Ugrad. Comp. Science student - "Windows? Linux and X!" Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Qmail Queue mounted via NFS?
+ "Robert J. Adams" [EMAIL PROTECTED]: | Is it possible to have two machines accessing the same queue via NFS? No! Your single copy of qmail-send assumes it is the only entity making any changes in the queue (with the exception of qmail-queue, which does however follow a specific protocol for inserting new messages). Break that assumption, and you're breaking qmail. You should always have the queue on a local disk anyway, for reliability as well as efficiency considerations. - Harald
Re: Qmail Queue mounted via NFS?
Harald, If we are speaking about reliability.. what if the local machine croaks.. then anything in the queue (of that local machine) is lost.. that isn't acceptable. -j --- Robert J. Adams [EMAIL PROTECTED] http://www.siscom.net Looking to outsource news? http://www.newshosting.com SISCOM Network Administration - President, SISCOM Inc. Phone: 937-222-8150 FAX: 937-222-8153 -Original Message- From: Harald Hanche-Olsen [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Tuesday, April 20, 1999 3:24 PM Subject: Re: Qmail Queue mounted via NFS? + "Robert J. Adams" [EMAIL PROTECTED]: | Is it possible to have two machines accessing the same queue via NFS? No! Your single copy of qmail-send assumes it is the only entity making any changes in the queue (with the exception of qmail-queue, which does however follow a specific protocol for inserting new messages). Break that assumption, and you're breaking qmail. You should always have the queue on a local disk anyway, for reliability as well as efficiency considerations. - Harald
Re: Qmail Queue mounted via NFS?
On Tue, 20 Apr 1999, Harald Hanche-Olsen wrote: + "Robert J. Adams" [EMAIL PROTECTED]: | Is it possible to have two machines accessing the same queue via NFS? No! Your single copy of qmail-send assumes it is the only entity making any changes in the queue (with the exception of qmail-queue, which does however follow a specific protocol for inserting new messages). Break that assumption, and you're breaking qmail. You should always have the queue on a local disk anyway, for reliability as well as efficiency considerations. Amen. You can use an NFS filestore for mail drops if you use Maildir, but definitely not the queue. You'd run a very high risk of corrupting messages in the queue if you NFS'd it across machines. jms
Re: Qmail Queue mounted via NFS?
On Tue, 20 Apr 1999, Robert J. Adams wrote: If we are speaking about reliability.. what if the local machine croaks.. then anything in the queue (of that local machine) is lost.. that isn't acceptable. Not necessarily. If the queue disk wasn't blown out when the machine croaked, then you can force a run of the queue when the machine comes back up and you're in good shape. That said, how would you distribute the queue across several machines, performance and reliability questions aside? NFS won't do it, I'll tell you that much. What if your central server were to croak in the middle of injecting a message into the queue (e.g. physically committing it to disk)? Same rules apply... If your central server were to go down, none of the machines could adequately function because they couldn't contact the host machine to insert a message into the queue. That would actually detract from reliability because your whole mail cluster would depend on having one machine up and accessible at all times. There are options for distributing filesystems using more than one central server (Coda, Transarc's AFS/DFS, etc), but these are either not totally production-ready, support only a very limited number of platforms, or their performance in write-intensive applications such as a mail queue isn't known. I'll accept the gamble of having a separate queue on each machine rather than one large centralized queue. An NFS mailstore, with RAID 0+1 queue is acceptable for my needs. jms
Re: Qmail queue stuck all the time, any ideas ?
I am running into some strange qmail behavior. I have configured qmail under tcpserver. Queues are permanently stuck and messages keep accruing in the queue. When the machine is rebooted, tcpserver starts, apparently qmail also does, but qmail dies. Apparently? You don't know? What interpretation have you made of the logs? During reboot or any time I restart qmail, I get a handful of messages that are delivered but are never cleared from the queue. In other words, if I reboot again, I get the same set of messages again from the queue. Also, kill -ALRM or running tcp_ok seems to make absolutely no sense. When I run qmail-qstat, all messages are shown as being in queue, with 0 messages not yet preprocessed (value 0 is true all the time). When I restart qmail manually, I do see all the processes such as qmail-send, rspawm, lspawn, splogger, etc. As explained earlier, qmail does not stay up after a reboot but tcpserver does. Any ideas, tips will be appreciated. I also tried doing a make setup check without any success. Show us what it generated. There is no point in trying to delivery mail if "make check" fails. If you mean that it didn't fail, then show us some logs of the delivery attempts. Show us some ps output of all qmail processes. Show us a process trace of qmail-send. In other words, we don't want a paraphrase of your problem, show us some real data if you wish to have some hope of a useful reply. Regards.
Re: qmail-queue _exit(61) when run by root
At 04:15 PM Wednesday 3/31/99, [EMAIL PROTECTED] wrote:
Hello,
I built qmail V1.03 on a Solaris 2.5.1 (SPARC) machine.
All went well, but when I tried to do some tests, a strange behaviour
appeared. I was successfully able to do a local-to-local delivery running
the following command as "pv" (a local non-privileged username):
echo to: pv | /var/qmail/bin/qmail-inject
But when I tried to run the same command as root, it failed with the
message:
qmail-inject: fatal: qq trouble in home directory (#4.3.0)
I looked into the syslog file: nothing.
I traced the run with truss(1), with the following command:
truss -iafe sh -c 'echo to: pv | /var/qmail/bin/qmail-inject' 21
and this is (part of) the output:
1244: chdir("/usr/local/qmail") = 0
1248: chdir("/usr/local/qmail") = 0
1248: execve("bin/qmail-queue", 0x0002A530, 0xED8C) argc = 1
1248: *** SUID: ruid/euid/suid = 0 / 500 / 500 ***
1248: chdir("/usr/local/qmail") Err#13 EACCES
1248: _exit(61)
% ls -lad / /usr /usr/local /usr/local/qmail
drwxr-sr-x 23 root root1024 Mar 31 11:25 /
drwxrwxr-x 31 root sys 1024 Oct 20 1997 /usr
drwx--lr-x 17 root sys 512 Mar 29 11:19 /usr/local
drwxr-xr-x 10 root qmail512 Mar 30 13:04 /usr/local/qmail
Is root in the supplementary group sys?
Do this:
# chmod g+rx /usr/local
(Given you have o=rx, I'm assuming you don't mind the permission issue of g+rx)
Supplementary groups are not relinquished when a setuid program executes and
group 'sys' has no access to /usr/local
If you cannot g+rx, you'll need to move the qmail directory out from
underneath /usr/local
That's my first guess anyway, it's been a while since I've look at this sort
of thing in great detail.
Regards.
Re: Qmail Queue Help
Hmmm, don't you mean '/var/qmail/queue/lock' ? On Tue, 12 Jan 1999, Frederic Woodbridge wrote: -BEGIN PGP SIGNED MESSAGE- Hello everyone. I think I just did a Really Stupid Thing! (tm) but I don't know how stupid yet. We had all these messages in the queue and we decided to flush them all. We got rid of the /var/qmail/queue/info/[0-22]/*, mess/[0-22]/* and remote/[0-22]/* files We restarted qmail (qmail-send) and now, we can't find /var/qmail/lock/* files (which I assume are important) and qmail is not responding. What can we do? I'd appreciate any help. Cheers, Frederic Woodbridge -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.0.2 iQEVAwUBNpuU3Jpk3It2CJ13AQGN+ggAo1amfFIvOKcuPuYha6ht7i9GLQlXCaKd e5PVfX68VLVMiDDUgvlaIsGpGLLMPSGWcYNCvhZXIAgQWUOSANc0kUwtjYlqwgPR pOvA/DzXM/A93e1m1/RC3k/+fzp3AxgPihcz2HpZeybtc7Gd7f1VwCMHbnI5DZL5 WgFB+MNx5IlDAldzN4Yv6OOEcOInp0nMsEQJF7J0CPjhgKSD4k73nBCYGbbEi8pV sd921GTSexStNHSAxLzzpYhubZaVzaFuu2EHr0cGTu25p3PQEDKyNyLq7H2Jr1VE q9XAeCRig+v1b9I5oJluebReOdxrWBLmJlm3B6jXU4Grz9MK9zag9w== =lsb5 -END PGP SIGNATURE-
Re: Qmail Queue Help
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 01:36 PM 1/12/99 , you wrote: Hmmm, don't you mean '/var/qmail/queue/lock' ? Yuppers, I do. Sorry. Fred -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.0.2 iQA/AwUBNpuXlSWLl68ykPinEQKMdACgih4Iz/tee7+dyN7XBMccUmFjCigAn3rl wpiafoVQqaQm9PHqx3M7Q6hp =q6+G -END PGP SIGNATURE-
Re: Qmail Queue Help
-BEGIN PGP SIGNED MESSAGE- At 01:34 PM 1/12/99 , you wrote: Stop qmail-send. "make setup check". Run qmail-start. -- Jeff Say, that did it! Thanks for the information, Jeff. You're a life-saver!! Fred. -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.0.2 iQEVAwUBNpuZZ5pk3It2CJ13AQGxIAf+Ne77RJIIkXyIYmCkQy8q08kR+OH72ceM lCd0qW1DqjNHLymxx2roKnASJstZ1rSwiX9wqRUW/aygapA6xbGS7P5PhLwyummg AlKPJ2bDvvNkVh3bsguO1fof6sIQc2vtUeaMx637qBiyVFKZh9SrVCaIwPcaZNmE 6rmEe8uQrqJi3UGU+NtZj3YHVZfLjQlaNW3XP3MaV4mZ4CYTb8gs5s8itGwFNHOR KtwaCB+GMZaUh6GAdBUDiorwmqvKNGIvuoZfzTzQA6ajeFsGqUjTWEkN5DA65sFN /Q4Q/Skel6GlhMLeFiA6lCtv+YSVdWkPcEhI8T4T9jzmvRijrgZfag== =B3Aw -END PGP SIGNATURE-
Re: Qmail Queue Help
Then get queue-fix from the qmail homepage. It should sort out your woes. Cya, John. On Tue, 12 Jan 1999, Frederic Woodbridge wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 01:36 PM 1/12/99 , you wrote: Hmmm, don't you mean '/var/qmail/queue/lock' ? Yuppers, I do. Sorry. Fred -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.0.2 iQA/AwUBNpuXlSWLl68ykPinEQKMdACgih4Iz/tee7+dyN7XBMccUmFjCigAn3rl wpiafoVQqaQm9PHqx3M7Q6hp =q6+G -END PGP SIGNATURE-
