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/ ---
Where to store extended envelope info in /var/qmail/queue ?
Vanilla qmail 1.03 stores the envelope sender address (preceded by an F and followed by a NUL) in a file in the directory /var/qmail/info/. RFC 1869 (SMTP Service Extensions) allows one to pass additional information on the MAIL command line after the FROM:address . Some of this information should in principle be passed on to qmail-local and/or qmail-remote for correct processing. (One example is BODY=8BITMIME. Regardless of how one thinks qmail-remote should behave when relaying to a server that doesn't advertise 8BITMIME --- I don't wish to revive *that* discussion --- it may be nice to pass on the 8BITMIME flag to those servers that do claim to support it --- but only if it was set on the inbound message; qmail-remote shouldn't try to compute it from the message content.) In the INTERNALS file, DJB wrote inter alia: Currently info/457 serves two purposes: first, it records the envelope sender; second, its modification time is used to decide when a message has been in the queue too long. In the future info/457 may store more information. Any non-backwards-compatible changes will be identified by version numbers. I think I may have a need to store more information. I would like to do so in a manner that won't clash with future official qmail releases. Would it be OK to store the information after the F...\0 envelope sender, as a (possibly empty) list of P...\0 parameters? Or am I better off creating a separate file xinfo/457 ? Sergio Gelato
qmail-queue question
Ive got a slight problem here and hoping that someone can help solve this. Due to a high volume of stupid users and mailing list addicts on our network (a small isp) we tend to get a lot of bounced messages, or messages to address that dont exist or what have you. The problem here is that they start to fill the queue up pretty fast. Now this isnt that big of a problem anymore since I raised our connection limit way the hell up there. 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? Just to answer all the simple questions: Q. Is the file readable by qmail? A. -rw-r--r-- 1 root qmail 7 Jul 20 18:06 queuelifetime 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 Q. Is it bouncing? A. Output from mailq | grep 112535 : 31 Jul 2001 01:01:12 GMT #112535 15511 emailAddressTrimmed 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 Im 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 qmails trying to send it works just fine and I dont get any errors or return codes.) Any thoughts would be appreciated. Later, Ed McLain High Speed Solutions
Re[2]: qmail-queue and custom reject message
posibly, must be a method to return message to qmail-smtpd from qmail-queue module... but i don't find it at this time. -- Best regards, vlad mailto:[EMAIL PROTECTED]
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
qmail-queue and custom reject message
hello guys. can anybody review, how i can give to message sender custom message during sending mail via my smtp server? current state is: 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? -- Best regards, vlad mailto:[EMAIL PROTECTED]
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: Inode allocation / qmail-queue?
On Mon, Jul 23, 2001 at 02:41:22PM -0600, Mike Hodson wrote: Hello there. I have been noticing slightly out of the ordinary things happening in my qmail-send logs after changing the queue filesystem over to reiserfs. I am seeing the same inode used for multiple messages. Is this normal? Yes, this is perfectly normal. Once a message is delivered, an inode number becomes available. Depending on how a filesystem allocates inodes, this may mean the number is immediately reused. If you have lots of logfiles from qmail running on an ext2fs disk, I guarantee you will see some inode-numbers being used more than once too. Greetz, Peter -- Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: several /var/qmail/bin/qmail-smtpd and bin/qmail-queue
bash-2.05$ ls -al /var/qmail/doc/INTERNALS ls: /var/qmail/doc/INTERNALS: No such file or directory bash-2.05$ - Original Message - From: Greg White [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 23, 2001 10:23 PM Subject: Re: several /var/qmail/bin/qmail-smtpd and bin/qmail-queue On Mon, Jul 23, 2001 at 09:58:04PM -0400, alexus wrote: i was checking something and i founds this my mail server seems to have tons of /var/qmail/bin/qmail-smtpd and bin/qmail-queue running at the same time.. about 30 of them The process actually listening on port 25 forks a qmail-smtpd for every incoming conneciton. qmail-queue is then run to place the mail safely in the queue. any ideas why? Read /var/qmail/doc/INTERNALS. nothin intersting in maillog I find that hard to believe. At the moment you see that many qmail-queues hanging around, qmail-smtpd's logs should read something like so, if logged through tcpserver: @40003b5cd7620a221bcc tcpserver: status: 30/xx where xx is either 40 or whatever is specified in the 'run' file for qmail-smtpd. ISTR that inetd does some sort of logging of how many processes it has opened, but it's been so long since I used inetd for anything that I've forgotten. -- Greg White
Re: several /var/qmail/bin/qmail-smtpd and bin/qmail-queue
On Tue, Jul 24, 2001 at 01:23:13PM -0400, alexus wrote: bash-2.05$ ls -al /var/qmail/doc/INTERNALS ls: /var/qmail/doc/INTERNALS: No such file or directory bash-2.05$ Apologies. Installing those files in /var/qmail/doc is a port-ism from FreeBSD. It's in the source tree only in a default install. GW -- Greg White
Re: Inode allocation / qmail-queue?
Hi Mike, this is a known issue with ReiserFS. As you might now, Ext2 and ReiserFS have many differences and you are just experiencing one of them. The whole problem is documented unter www.namesys.com (the homepage of ReiserFS) so you will find the information you need there. In general you have two options: 1) Moving the qMail partition back to ext2 (probably /var) 2) Patching qMail with the ReiserFS patch. (I think that one is available through a link on www.namesys.com too). Just for your information: I have a linux box running qMail and I have moved /home which contains the pop-boxes to ReiserFS but /var remains ext2. This makes sure that mail is securely stored once it is delivered and if your queue (or the partition) crashed you won't have much chances to restore it anyway. Hope this help, Lordy At 14:41 23.07.2001 -0600, you wrote: Hello there. I have been noticing slightly out of the ordinary things happening in my qmail-send logs after changing the queue filesystem over to reiserfs. I am seeing the same inode used for multiple messages. Is this normal? (other users email has been blanked, as has all senders. mine is known to all of you, so why bother typing to cover mine eh? ) excerpts from my qmail-queue log piped thru tai64nlocal 2001-07-23 14:29:38.294512500 new msg 405006 2001-07-23 14:29:38.294529500 info msg 405006: bytes 2531 from [EMAIL PROTECTED] qp 28395 uid 1016 2001-07-23 14:29:38.388694500 starting delivery 689: msg 405006 to local vdomain-vuser@vdomain 2001-07-23 14:29:38.388713500 status: local 1/10 remote 0/20 2001-07-23 14:29:38.442249500 delivery 689: success: POP_user_does_not_exist,_but_will_deliver_to_/users/catchall/dir/did_0+0+1/ 2001-07-23 14:29:38.442273500 status: local 0/10 remote 0/20 2001-07-23 14:29:38.442278500 end msg 405006 2001-07-23 14:32:30.228899500 new msg 405006 2001-07-23 14:32:30.228916500 info msg 405006: bytes 4242 from [EMAIL PROTECTED] qp 28405 uid 1016 2001-07-23 14:32:30.305868500 starting delivery 690: msg 405006 to local [EMAIL PROTECTED] 2001-07-23 14:32:30.305886500 status: local 1/10 remote 0/20 2001-07-23 14:32:30.376295500 delivery 690: success: did_0+0+1/ 2001-07-23 14:32:30.376313500 status: local 0/10 remote 0/20 2001-07-23 14:32:30.376319500 end msg 405006 2001-07-23 14:32:32.722033500 new msg 405006 2001-07-23 14:32:32.722049500 info msg 405006: bytes 1827 from [EMAIL PROTECTED] qp 28409 uid 1016 2001-07-23 14:32:32.814920500 starting delivery 691: msg 405006 to local [EMAIL PROTECTED] 2001-07-23 14:32:32.814937500 status: local 1/10 remote 0/20 2001-07-23 14:32:32.847071500 delivery 691: success: did_0+0+1/ 2001-07-23 14:32:32.847089500 status: local 0/10 remote 0/20 2001-07-23 14:32:32.847094500 end msg 405006 Mike -- Mike Hodson [EMAIL PROTECTED]
Re: Inode allocation / qmail-queue?
Er whatever other issues may or may not be associated with ReiserFS, re-use of inodes does not present a problem for qmail and is commonly seen on UFS. If you look at the log fragment carefully you'll see that the inode is only reused after the message has been delivered and thus the file deleted. It would be a problem if the same inode was in use at the same time, but the log fragment doesn't show that. By way of an example, on a FreeBSD 4.2 UFS queue I see that the same inode has been re-used over 100 times for some 1200 deliveries. $ grep 'info msg' /var/log/qmail/current | cut -f4 -d' ' | cut -f1 -d: | sort -n | uniq -c | sort -nr 177 8097707 165 8097716 118 8097715 83 8097913 75 8097709 71 8097768 62 8097947 48 8097699 42 8097909 33 8097990 29 8097701 23 8097755 16 8097879 16 8097769 15 8097910 14 8097943 14 8097914 14 8097712 13 8097719 11 8097753 10 8097998 10 8097997 8 8097984 ... Regards. On Tue, Jul 24, 2001 at 01:45:57AM +0200, Lordy allegedly wrote: Hi Mike, this is a known issue with ReiserFS. As you might now, Ext2 and ReiserFS have many differences and you are just experiencing one of them. The whole problem is documented unter www.namesys.com (the homepage of ReiserFS) so you will find the information you need there. In general you have two options: 1) Moving the qMail partition back to ext2 (probably /var) 2) Patching qMail with the ReiserFS patch. (I think that one is available through a link on www.namesys.com too). Just for your information: I have a linux box running qMail and I have moved /home which contains the pop-boxes to ReiserFS but /var remains ext2. This makes sure that mail is securely stored once it is delivered and if your queue (or the partition) crashed you won't have much chances to restore it anyway. Hope this help, Lordy At 14:41 23.07.2001 -0600, you wrote: Hello there. I have been noticing slightly out of the ordinary things happening in my qmail-send logs after changing the queue filesystem over to reiserfs. I am seeing the same inode used for multiple messages. Is this normal? (other users email has been blanked, as has all senders. mine is known to all of you, so why bother typing to cover mine eh? ) excerpts from my qmail-queue log piped thru tai64nlocal 2001-07-23 14:29:38.294512500 new msg 405006 2001-07-23 14:29:38.294529500 info msg 405006: bytes 2531 from [EMAIL PROTECTED] qp 28395 uid 1016 2001-07-23 14:29:38.388694500 starting delivery 689: msg 405006 to local vdomain-vuser@vdomain 2001-07-23 14:29:38.388713500 status: local 1/10 remote 0/20 2001-07-23 14:29:38.442249500 delivery 689: success: POP_user_does_not_exist,_but_will_deliver_to_/users/catchall/dir/did_0+0+1/ 2001-07-23 14:29:38.442273500 status: local 0/10 remote 0/20 2001-07-23 14:29:38.442278500 end msg 405006 2001-07-23 14:32:30.228899500 new msg 405006 2001-07-23 14:32:30.228916500 info msg 405006: bytes 4242 from [EMAIL PROTECTED] qp 28405 uid 1016 2001-07-23 14:32:30.305868500 starting delivery 690: msg 405006 to local [EMAIL PROTECTED] 2001-07-23 14:32:30.305886500 status: local 1/10 remote 0/20 2001-07-23 14:32:30.376295500 delivery 690: success: did_0+0+1/ 2001-07-23 14:32:30.376313500 status: local 0/10 remote 0/20 2001-07-23 14:32:30.376319500 end msg 405006 2001-07-23 14:32:32.722033500 new msg 405006 2001-07-23 14:32:32.722049500 info msg 405006: bytes 1827 from [EMAIL PROTECTED] qp 28409 uid 1016 2001-07-23 14:32:32.814920500 starting delivery 691: msg 405006 to local [EMAIL PROTECTED] 2001-07-23 14:32:32.814937500 status: local 1/10 remote 0/20 2001-07-23 14:32:32.847071500 delivery 691: success: did_0+0+1/ 2001-07-23 14:32:32.847089500 status: local 0/10 remote 0/20 2001-07-23 14:32:32.847094500 end msg 405006 Mike -- Mike Hodson [EMAIL PROTECTED]
Re: Inode allocation / qmail-queue?
On Tue, Jul 24, 2001 at 01:45:57AM +0200, Lordy wrote: Hi Mike, this is a known issue with ReiserFS. As you might now, Ext2 and ReiserFS have many differences and you are just experiencing one of them. The whole problem is documented unter www.namesys.com (the homepage of ReiserFS) so you will find the information you need there. Hmm, according to the ReiserFS FAQ (http://www.namesys.com/faq.html#qmail), the only issue affecting ReiserFS is the same one affecting ext2: namely that link() and unlink() are synchronous operations. I see no special problems... I'm currently about to go live with new ReiserFS based Qmail servers, and haven't noticed any problem. If there is, I'd certainly like to know... :-) -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
Re: Inode allocation / qmail-queue?
On Tue, Jul 24, 2001 at 01:30:01PM +1200, Jason Haar wrote: I'm currently about to go live with new ReiserFS based Qmail servers, and haven't noticed any problem. If there is, I'd certainly like to know... :-) I'm running qmail on several boxen, all ReiserFS-only. Not a single problem to date, though I did use Bruce Guenter's syncdir patch, so that could be construed as cheating. 8-) Also read the Qmail-ReiserFS Integration HOWTO: http://www.jedi.claranet.fr/qmail-reiserfs-howto.html. -- Adrian HoTinker, Drifter, Fixer, Bum [EMAIL PROTECTED] Archived @: http://marc.theaimsgroup.com/?l=qmail Useful URLs: http://cr.yp.to/qmail.html http://www.qmail.org http://www.lifewithqmail.org/ http://qmail.faqts.com/
several /var/qmail/bin/qmail-smtpd and bin/qmail-queue
i was checking something and i founds this my mail server seems to have tons of /var/qmail/bin/qmail-smtpd and bin/qmail-queue running at the same time.. about 30 of them any ideas why? nothin intersting in maillog
Re: several /var/qmail/bin/qmail-smtpd and bin/qmail-queue
On Mon, Jul 23, 2001 at 09:58:04PM -0400, alexus wrote: i was checking something and i founds this my mail server seems to have tons of /var/qmail/bin/qmail-smtpd and bin/qmail-queue running at the same time.. about 30 of them The process actually listening on port 25 forks a qmail-smtpd for every incoming conneciton. qmail-queue is then run to place the mail safely in the queue. any ideas why? Read /var/qmail/doc/INTERNALS. nothin intersting in maillog I find that hard to believe. At the moment you see that many qmail-queues hanging around, qmail-smtpd's logs should read something like so, if logged through tcpserver: @40003b5cd7620a221bcc tcpserver: status: 30/xx where xx is either 40 or whatever is specified in the 'run' file for qmail-smtpd. ISTR that inetd does some sort of logging of how many processes it has opened, but it's been so long since I used inetd for anything that I've forgotten. -- Greg White
Re: several /var/qmail/bin/qmail-smtpd and bin/qmail-queue
i can send you today's log.. but its really nothing intersting there what i found intesting is tcpserver servver shows 0/40 - Original Message - From: Greg White [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 23, 2001 10:23 PM Subject: Re: several /var/qmail/bin/qmail-smtpd and bin/qmail-queue On Mon, Jul 23, 2001 at 09:58:04PM -0400, alexus wrote: i was checking something and i founds this my mail server seems to have tons of /var/qmail/bin/qmail-smtpd and bin/qmail-queue running at the same time.. about 30 of them The process actually listening on port 25 forks a qmail-smtpd for every incoming conneciton. qmail-queue is then run to place the mail safely in the queue. any ideas why? Read /var/qmail/doc/INTERNALS. nothin intersting in maillog I find that hard to believe. At the moment you see that many qmail-queues hanging around, qmail-smtpd's logs should read something like so, if logged through tcpserver: @40003b5cd7620a221bcc tcpserver: status: 30/xx where xx is either 40 or whatever is specified in the 'run' file for qmail-smtpd. ISTR that inetd does some sort of logging of how many processes it has opened, but it's been so long since I used inetd for anything that I've forgotten. -- Greg White
RE: help! thousands of qmail-queue processes!
The vast majority of the qmail-queue processes look to have a parent pid of '1' Maybe 1% of the queue processes have other parent pids, so I'm not too worried about them. The server is still delivering some mail, so I'm making an educated guess that queue processes not attached to init are doing The Right Thing. Thanks, Chris McDaniel -Original Message- From: Alex Pennace [mailto:[EMAIL PROTECTED]] Sent: 19 Jul, 2001 2:51 PM To: Chris McDaniel Cc: '[EMAIL PROTECTED]' Subject: Re: help! thousands of qmail-queue processes! On Thu, Jul 19, 2001 at 10:43:14AM -0600, Chris McDaniel wrote: I'm having trouble with qmail - I have about 500 messages in the queue (usually this number hovers between 50 and 80) and between 1000 and 2000 qmail-queue processes hanging around depending on when I sample. What are the parents of those qmail-queue processes, and what are they doing?
Re: help! thousands of qmail-queue processes!
On Thu, Jul 19, 2001 at 01:07:21PM -0600, Chris McDaniel wrote: The vast majority of the qmail-queue processes look to have a parent pid of '1' Then something is not running qmail-queue properly. Find out what. Shortly after it starts, qmail-queue starts a message file under queue/mess. Even if no content has been passed to qmail-queue yet, it will write out its Received header, which includes the calling uid. Start your investigation there.
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/ ---
ANN: queue_repair v.0.8.0 -- yet another qmail queue repair tool
Greetings, This is the first public release of queue_repair, which is yet another qmail queue repair tool. Features include: -written in Python; no compilation necessary. -automatic, dynamic determination of UIDs and GIDs. -automatic, dynamic determination of conf-split; can be overridden on the commandline to change the conf-split of an existing queue without running a parallel, temporary instance of qmail for queuelifetime. Just recompile and stop qmail, run queue-repair, and restart qmail. -automatic, dynamic determination of use of big-todo; can be overridden on the commandline to change an existing queue as above. -handles basic tasks like fixing a queue restored from backups, incorrect ownership or permissions of directories and files, missing or extra split subdirectories, unexpected files or other direntries, or creating a valid queue from scratch. -can run in repair or test (report-only) modes. The default is test mode. -can also be imported as a library from other Python scripts. All functionality is available for customized uses this way. -licensed under the GNU General Public License version 2. queue_repair is available for download at http://www.qcc.sk.ca/~charlesc/software/queue_repair/ I would appreciate any feedback on queue_repair. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Using qmail-queue
Jon [EMAIL PROTECTED] wrote: My company runs quite a large opt-in newsletter (around 60,000 members, growing by about a 1000 every few days), up to a few months ago we sent the newsletter by using qmail-inject for every email address on the list (which was slow). So we started to use the qmail-queue directly (using the info on the man page for it) so we give qmail-queue the message file with all the headers, and also the list of email addresses. Work well, and super fast :-) But last week one of our bosses found that Hotmail has a bulk mail folder so all incoming email to Hotmail users which does not have there email address in the To: field of the email, goes into this folder. And because we use qmail-queue, all the emails sent has the same To: fieild (we use the email address for our site)and therefore all our newsletters go into there bulk folder. You're sending bulk mail, which Hotmail is correctly identifying as bulk mail--but you want to trick it into thinking your mail is not bulk. If this is an opt-in newsletter, why do you care that Hotmail identifies it as bulk? -Dave
Using qmail-queue
Hi, My company runs quite a large opt-in newsletter (around 60,000 members, growing by about a 1000 every few days), up to a few months ago we sent the newsletter by using qmail-inject for every email address on the list (which was slow). So we started to use the qmail-queue directly (using the info on the man page for it) so we give qmail-queue the message file with all the headers, and also the list of email addresses. Work well, and super fast :-) But last week one of our bosses found that Hotmail has a bulk mail folder so all incoming email to Hotmail users which does not have there email address in the To: field of the email, goes into this folder. And because we use qmail-queue, all the emails sent has the same To: fieild (we use the email address for our site)and therefore all our newsletters go into there bulk folder. So is there anyway of having the email address of the user being emailed in the To: field without using qmail-inject for every message? Looking at this mailing list (which uses ezmlm) it seems everyone has there own Return-Path made up of my email address on this list. So if its possable to have a different return-path for every email, is it possable to change the To header and still use qmail-queue? Any ideas? We can't really use ezmlm as we have our very own customised software for our mailing list which we have built and added to for years. Thanks in advance, Jon
Re: Using qmail-queue
Jon [EMAIL PROTECTED] writes: Any ideas? We can't really use ezmlm as we have our very own customised software for our mailing list which we have built and added to for years. If you use qmail-queue directly anyway where is the problem to replace a placeholder string in the To: header during injection? sed would do but three lines of C should also. Regards, Frank
Re: Using qmail-queue
Jon writes: So is there anyway of having the email address of the user being emailed in the To: field without using qmail-inject for every message? You can use the following patch to qmail-remote, or if that's not sufficient, I have a proprietary patch which allows substitution of fields from a database, conditional substitution, paragraph reformatting, etc. It's a subset of the TRAC programming language, and could be extended to be such. liThere's also the a href=http://www.ezmlm.org/pub/patches/qmail-verh-0.02.tar.gz;qmail-verh patch/a. This allows substitution of the recipient local/host parts into the message. Useful for inserting a customized mailto: URL for list-unsubscribe into the body of the message. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | John Hartford, RIP Potsdam, NY 13676-3213 | +1 315 268 9201 FAX |
Re: Using qmail-queue
So is there anyway of having the email address of the user being emailed in the To: field without using qmail-inject for every message? Using plain qmail, no, it tries very hard no to mutate messages as they pass through. For a similar application I wrote a little perl module called qspam to send out lots of customized messages. It passes each message directly to qmail-remote, and only if that fails passes it to qmail-queue to retry. It runs many qmail-remote processes in parallel, and on any half-decent list rarely has to queue a message so it pumps out mail about as fast as qmail itself does. For me it does a pretty decent job of sending out messages to an 18,000 address list I have. It uses files in /tmp rather than pipes because that makes the code a lot simpler and it seems to me that files in a ramdisk /tmp should be about as fast as pipes. You can find it at http://wx.iecc.com/Qspam.pm -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 [EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
Re: how to use qmail-queue
On Sat, Jun 09, 2001 at 11:18:54AM -0600, Charles Cazabon wrote: However, QMTP, as a protocol, is harder to speak than SMTP Arguable, at best. For sending a single message, the only difficult part of QMTP is calculating the total sizes before sending the package. After that point, you just send all the data and wait for the response. The server is forbidden from sending a response until the last byte of the package is received. Much simpler than the back-and-forth of SMTP. However, this does nothing to answer his original problem, which is likely solveable without dealing with any external protocols. -- Bruce Guenter [EMAIL PROTECTED] http://em.ca/~bruceg/ http://untroubled.org/ OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8 PGP signature
how to use qmail-queue
Hi everyone I'm still trying to utilize qmail with my web based mailing list. my ideas. 1. instead of using mail program /usr/sbin/sendmail I wanted to use /var/qmail/bin/qmail-qmtpd to send mail and it did not work. 2. Okay how about this, instead of sending these mails directly, I want to queue them first and send later. say I have 1000 emails in my mysql database, when I try to loop through the emails and trying to send the mails at the same time takes too long. I can't have everyone wait long time since the mailing stops when someone closes out the browser. so is there a way to just queue them and have it send on the back groud. does anyone know how to do this. Is there more documentation on qmail-queue. recap: instead directly trying to send mails, I would like to queue them initially and have qmail send mails in the back ground so no one has to wait to finish sending mails but just wait to finish queue them. thanks in advance --Sudong
Re: how to use qmail-queue
newbieportal [EMAIL PROTECTED] wrote: I'm still trying to utilize qmail with my web based mailing list. my ideas. 1. instead of using mail program /usr/sbin/sendmail I wanted to use /var/qmail/bin/qmail-qmtpd to send mail and it did not work. Why? qmail-qmtpd is a daemon that accepts mail over the network, much like qmail-smtpd. However, QMTP, as a protocol, is harder to speak than SMTP (as Dan says, it was designed for speed, not simplicity). Using QMTP buys you nothing over speaking SMTP, or, for that matter, using qmail's sendmail wrapper, qmail-inject, or qmail-queue. What problem are you trying to solve? In other words, what is it about qmail's sendmail wrapper that prevents you from using it? 2. Okay how about this, instead of sending these mails directly, I want to queue them first and send later. say I have 1000 emails in my mysql database, when I try to loop through the emails and trying to send the mails at the same time takes too long. I can't have everyone wait long time since the mailing stops when someone closes out the browser. so is there a way to just queue them and have it send on the back groud. If it's the same message going to 1000 recipients (as opposed to 1000 different messages going to one recipient each), you're doing it incorrectly and inefficiently. Just feed the message to qmail-inject (or the sendmail wrapper) with all recipients in one message. Open a pipe to qmail-inject and send the message: From: address@domain Subject: List message To: recipient list not shown: ; bcc: recipient1@domain1 bcc: recipient2@domain2 ... bcc: recipient1000@domain1000 Hi! This is a list message. And that will do it quickly and efficiently. does anyone know how to do this. Is there more documentation on qmail-queue. You can, of course, use qmail-queue directly (the man page for qmail-queue is sufficient for using it; I've done it) but it doesn't buy you much in this case. recap: instead directly trying to send mails, I would like to queue them initially and have qmail send mails in the back ground so no one has to wait to finish sending mails but just wait to finish queue them. qmail always does this. There is no non-queued delivery mode in 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: Please tele me every sub-directory meaning in /var/qmail/queue/ .
george [EMAIL PROTECTED] wrote: It have some sub-directory in /ar/qmail/queue directory .But I don't know every directory content and meaning . Anyone can tele me? See: http://www.lifewithqmail.org/lwq.html#file-structure -Dave
Re: Please tele me every sub-directory meaning in /var/qmail/queue/ .
george [EMAIL PROTECTED] wrote: It have some sub-directory in /ar/qmail/queue directory .But I don't know every directory content and meaning . The file INTERNALS in the documentation included in the qmail tarball explains what these directories are for. 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. ---
Please tele me every sub-directory meaning in /var/qmail/queue/ .
Hello all: It have some sub-directory in /ar/qmail/queue directory .But I don't know every directory content and meaning . Anyone can tele me? Thank you! # ls -l /var/qmail/queue/ total 18 drwx-- 2 qmails qmail512 May 31 09:43 bounce drwx-- 25 qmails qmail512 May 30 10:45 info drwx-- 2 qmailq qmail512 May 31 09:43 intd drwx-- 25 qmails qmail512 May 30 10:45 local drwxr-x--- 2 qmailq qmail512 May 30 10:45 lock drwxr-x--- 25 qmailq qmail512 May 30 10:45 mess drwx-- 2 qmailq qmail512 May 31 09:43 pid drwx-- 25 qmails qmail512 May 30 10:45 remote drwxr-x--- 2 qmailq qmail512 May 31 09:43 todo #
Re: Please tele me every sub-directory meaning in /var/qmail/queue/.
It have some sub-directory in /var/qmail/queue directory. But I don't know every directory content and meaning . Anyone can tell me? Thank you! # ls -l /var/qmail/queue/ total 18 drwx-- 2 qmails qmail512 May 31 09:43 bounce drwx-- 25 qmails qmail512 May 30 10:45 info drwx-- 2 qmailq qmail512 May 31 09:43 intd drwx-- 25 qmails qmail512 May 30 10:45 local drwxr-x--- 2 qmailq qmail512 May 30 10:45 lock drwxr-x--- 25 qmailq qmail512 May 30 10:45 mess drwx-- 2 qmailq qmail512 May 31 09:43 pid drwx-- 25 qmails qmail512 May 30 10:45 remote drwxr-x--- 2 qmailq qmail512 May 31 09:43 todo # In general, what you can not understand and can not find documentation about, you should not care about. Just let qmail-queue 'et al' handle this directory and enjoy your working qmail system. Or mess it up and get someone to help you out of trouble. BTW, qmail stores your emails and connecting infos in this directory. Regards. Csaba PS. Have you read any documentation about qmail before installing it? Life With Qmail for example worth reading. Find it at www.lifewithqmail.com __ This message went through virus scan at Trend Ltd. which stated the message was clean of viri appeared before 2001.05.24.
Re: injecting qmail-queue (asking again)
* Todd Finney [EMAIL PROTECTED] [010522 01:09]: I thought about that, but it isn't really an ezmlm question anymore. There doesn't seem to be an example on using qmail-queue anywhere. It seems to me that there probably should be. Fair enough. So make ezmlm-reject omit that behavior. `man ezmlm-reject` And give up the spam protection that this provides? No thanks :). There are ways of emulating this sort of spam protection with ezmlm-issubn; a couple have been mentioned on the ezmlm list. Check the archives at [http://marc.theaimsgroup.com/?l=ezmlm]. Eek, why not invoke ezmlm-send for each list? `man ezmlm-send` No need to mess with qmail-queue, I don't think. Yea, that sounds nice, but there isn't an example of using that outside of a .qmail file, either. I'd think that tfinney]$ cat ./list_monthly_announcement.txt | /usr/local/bin/ezmlm/ezmlm-send /home/list/test/ would work, but no dice. That is indeed the syntax. I'm still pretty convinced that this is the best way to do this; you might want to look into why that doesn't work, regardless of any other solution. I created my message file, message.txt, and my envelope file envelope.txt. AFAIK, they're in the correct format. [...] I tried three different formats. I believe the first is correct, but I saw a few mentioning of the other two, and tried them. I saw no difference in running the script with any of them. F [EMAIL PROTECTED]\0 T [EMAIL PROTECTED]\0 \0\0 This should be: [EMAIL PROTECTED]\[EMAIL PROTECTED]\0\0 Is that what you meant? open \*STDIN, MSG; open \*STDOUT, ENV; Er, off the top of my head, you want to reverse that wokka, since STDOUT is an output stream. Like: open \*STDIN, MSG; open \*STDOUT, ENV; Any luck with this? Anyway, it seems to be a lot of overkill. Just iterate over your lists and invoke ezmlm-send for each one. Done. Thanks, I'll look into that, but I think a little more explicit documentation on qmail-queue would be helpful. John Levine just threw together a Perl module that invokes qmail-queue directly. See [http://marc.theaimsgroup.com/?l=qmailm=99016757917465w=2]; it might be helpful. (I'm actually already using it...it is *really* nice. :-) /pg -- Peter Green : Architekton Internet Services, LLC : [EMAIL PROTECTED] --- Q. Why is this so clumsy? A. The trick is to use Perl's strengths rather than its weaknesses. --- Larry Wall in [EMAIL PROTECTED]
Re: injecting qmail-queue (asking again)
Asking again because, well, I'm still stumped.
Date: Sat, 19 May 2001 20:20:19 -0400
To: [EMAIL PROTECTED]
From: Todd Finney [EMAIL PROTECTED]
Subject: injecting qmail-queue
Before I go into detail about the problem I'm having, I'll describe
what I'm trying to do, to make sure that I'm even on the right track.
We host a number of lists running under ezmlm-idx. I want to send an
announcement out to all of the lists every month. I first tried to
do this with a list of lists, but ezmlm doesn't care for that
approach, because the list name doesn't wind up in the To: or Cc:
headers.
I'd rather not have things depend on the announcement process user
being a subscriber or in DIR/allow, which I think precludes the use of
qmail-inject. So, I'm attempting to do it with qmail-queue.
I created my message file, message.txt, and my envelope file
envelope.txt. AFAIK, they're in the correct format.
Looking back through the list, I saw Peter Green's example from a few
months ago, and came up with this:
#!/usr/bin/perl -w
use strict;
$|++;
my $mailprog = '/var/qmail/bin/qmail-queue';
my $message = './list_monthly_announcement.txt';
my $envelope = './list_monthly_announcement_recipients.txt';
open MSG,$message or die Failed to open message file $!;
open ENV,$envelope or die Failed to open envelope $!;
open \*STDIN, MSG;
open \*STDOUT, ENV;
my $rc = exec( $mailprog );
if ($rc) {
die $rc something happened;
}
This does nothing useful (nothing in the log, no message sent),
although I'm at a loss to explain why. I saw references to calling a
pipe() to do this properly, but I can't find an example. Does one
exist?
thanks,
Todd
Re: injecting qmail-queue (asking again)
Todd, this would do just as well (or better) on the ezmlm list, since a couple of the possible solutions use ezmlm-* rather than qmail-queue. * Todd Finney [EMAIL PROTECTED] [010521 23:12]: Before I go into detail about the problem I'm having, I'll describe what I'm trying to do, to make sure that I'm even on the right track. We host a number of lists running under ezmlm-idx. I want to send an announcement out to all of the lists every month. I first tried to do this with a list of lists, but ezmlm doesn't care for that approach, because the list name doesn't wind up in the To: or Cc: headers. So make ezmlm-reject omit that behavior. `man ezmlm-reject` I'd rather not have things depend on the announcement process user being a subscriber or in DIR/allow, which I think precludes the use of qmail-inject. So, I'm attempting to do it with qmail-queue. Eek, why not invoke ezmlm-send for each list? `man ezmlm-send` No need to mess with qmail-queue, I don't think. I created my message file, message.txt, and my envelope file envelope.txt. AFAIK, they're in the correct format. If you are asking for help, it would probably be best if you were complete in your setup. Don't assume something is in the right format: prove it by posting it. (Or put it up on the web and link to it.) This may or may not actually help in this scenario, but you are *asking* to get reamed by any number of people for mentioning the files but refusing to post them. FYI. Looking back through the list, I saw Peter Green's example from a few months ago, and came up with this: YAY I'M FAMOUS! ;-) #!/usr/bin/perl -w use strict; $|++; my $mailprog = '/var/qmail/bin/qmail-queue'; my $message = './list_monthly_announcement.txt'; my $envelope = './list_monthly_announcement_recipients.txt'; Again, here's where it would be REALLY helpful to see this text file. open \*STDIN, MSG; open \*STDOUT, ENV; Er, off the top of my head, you want to reverse that wokka, since STDOUT is an output stream. Like: open \*STDIN, MSG; open \*STDOUT, ENV; Ah yes, looking at `man perlopentut` would seem to indicate that format is right. Anyway, it seems to be a lot of overkill. Just iterate over your lists and invoke ezmlm-send for each one. Done. Good luck, /pg -- Peter Green : Architekton Internet Services, LLC : [EMAIL PROTECTED] --- linux: the choice of a GNU generation ([EMAIL PROTECTED] put this on Tshirts in '93)
Re: injecting qmail-queue (asking again)
At 11:32 PM 5/21/01, peter green wrote: Todd, this would do just as well (or better) on the ezmlm list, since a couple of the possible solutions use ezmlm-* rather than qmail-queue. I thought about that, but it isn't really an ezmlm question anymore. There doesn't seem to be an example on using qmail-queue anywhere. It seems to me that there probably should be. * Todd Finney [EMAIL PROTECTED] [010521 23:12]: We host a number of lists running under ezmlm-idx. I want to send an announcement out to all of the lists every month. I first tried to do this with a list of lists, but ezmlm doesn't care for that approach, because the list name doesn't wind up in the To: or Cc: headers. So make ezmlm-reject omit that behavior. `man ezmlm-reject` And give up the spam protection that this provides? No thanks :). I'd rather not have things depend on the announcement process user being a subscriber or in DIR/allow, which I think precludes the use of qmail-inject. So, I'm attempting to do it with qmail-queue. Eek, why not invoke ezmlm-send for each list? `man ezmlm-send` No need to mess with qmail-queue, I don't think. Yea, that sounds nice, but there isn't an example of using that outside of a .qmail file, either. I'd think that tfinney]$ cat ./list_monthly_announcement.txt | /usr/local/bin/ezmlm/ezmlm-send /home/list/test/ would work, but no dice. Anyway, that _is_ an ezmlm problem, and isn't our problem here. I created my message file, message.txt, and my envelope file envelope.txt. AFAIK, they're in the correct format. If you are asking for help, it would probably be best if you were complete in your setup. Don't assume something is in the right format: prove it by posting it. (Or put it up on the web and link to it.) This may or may not actually help in this scenario, but you are *asking* to get reamed by any number of people for mentioning the files but refusing to post them. FYI. I didn't refuse to post anything. :) Please don't say that I did. I didn't include the envelope file because it seemed secondary to the problem. If I can't figure out how to get qmail-queue to take input, what difference would it make what I'm feeding it? I tried three different formats. I believe the first is correct, but I saw a few mentioning of the other two, and tried them. I saw no difference in running the script with any of them. F [EMAIL PROTECTED]\0 T [EMAIL PROTECTED]\0 \0\0 F [EMAIL PROTECTED]\0 T [EMAIL PROTECTED]\0 \0\0 F[EMAIL PROTECTED]\0 T[EMAIL PROTECTED]\0 \0\0 #!/usr/bin/perl -w use strict; $|++; my $mailprog = '/var/qmail/bin/qmail-queue'; my $message = './list_monthly_announcement.txt'; my $envelope = './list_monthly_announcement_recipients.txt'; Again, here's where it would be REALLY helpful to see this text file. See above. open \*STDIN, MSG; open \*STDOUT, ENV; Er, off the top of my head, you want to reverse that wokka, since STDOUT is an output stream. Like: open \*STDIN, MSG; open \*STDOUT, ENV; Ah yes, looking at `man perlopentut` would seem to indicate that format is right. Anyway, it seems to be a lot of overkill. Just iterate over your lists and invoke ezmlm-send for each one. Done. Thanks, I'll look into that, but I think a little more explicit documentation on qmail-queue would be helpful. If I figure this out, I'll post an example to the list, so that we don't have to have this conversation again. cheers, Todd
injecting qmail-queue
Before I go into detail about the problem I'm having, I'll describe
what I'm trying to do, to make sure that I'm even on the right track.
We host a number of lists running under ezmlm-idx. I want to send an
announcement out to all of the lists every month. I first tried to do
this with a list of lists, but ezmlm doesn't care for that approach,
because the list name doesn't wind up in the To: or Cc: headers.
I'd rather not have things depend on the announcement process user
being a subscriber or in DIR/allow, which I think precludes the use of
qmail-inject. So, I'm attempting to do it with qmail-queue.
I created my message file, message.txt, and my envelope file
envelope.txt. AFAIK, they're in the correct format.
Looking back through the list, I saw Peter Green's example from a few
months ago, and came up with this:
#!/usr/bin/perl -w
use strict;
$|++;
my $mailprog = '/var/qmail/bin/qmail-queue';
my $message = './list_monthly_announcement.txt';
my $envelope = './list_monthly_announcement_recipients.txt';
open MSG,$message or die Failed to open message file $!;
open ENV,$envelope or die Failed to open envelope $!;
open \*STDIN, MSG;
open \*STDOUT, ENV;
my $rc = exec( $mailprog );
if ($rc) {
die $rc something happened;
}
This does nothing useful (nothing in the log, no message sent),
although I'm at a loss to explain why. I saw references to calling a
pipe() to do this properly, but I can't find an example. Does one
exist?
thanks,
Todd
Re: [OT] Sticky question about qmail-queue and qmail-smtpd interactions
* Andy Bradford [EMAIL PROTECTED] writes: Thus said Jason Haar on Fri, 20 Apr 2001 14:06:02 +1200: me to realise a rare error condition I hadn't expected. This virus scanner didn't like scanning a 90Mb zip'ped AVI file (ahem) - whereas another vendor scanner took 1.5minutes to scan it, this one took nearly two hours... Tell them to send MPEG instead. ;-) Excellent solution. If I read Jason correctly, though, his scanner is actually opening zip files. Jason, would you like a copy of 42.zip? You know, that's a 42k zip file with 10 zip files with 10 zip files with... Unzipping stuff on the server is, well, asking for trouble. -- Robin S. Socha http://my.gnus.org/ - To boldly frobnicate what no newbie has grokked before.
Sticky question about qmail-queue and qmail-smtpd interactions
Hi there I'm the author of Qmail-Scanner - an Email scanning harness that can be used to block attachments, scan for viruses, etc. It's hooked in as a replacement for qmail-queue. The installation of a rather slow virus scanner on my own systems had lead me to realise a rare error condition I hadn't expected. This virus scanner didn't like scanning a 90Mb zip'ped AVI file (ahem) - whereas another vendor scanner took 1.5minutes to scan it, this one took nearly two hours... The sending SMTP server's qmail-remote timed out the SMTP session after 20 minutes - as being in error - as it had waited "too long" for the final "OK". However, STDOUT on the receiving box still received the "mail from|rcpt to" envelope headers, so after 2 hours Qmail-Scanner happily delivered it back to the real qmail-queue for real delivery. However... back on the sending host, it tried to send it again... I had a little loop going there - quite nasty. Can you say "busy system"? :-) Anyhoo, the virus scanner is the real culprit here - and that's something that can be fixed (i.e. get another). The problem is WHY did the recipient qmail-smtpd send through the envelope headers via STDOUT to qmail-queue/Qmail-Scanner? Upon noticing the sender going away, shouldn't it have recognised that as an error condition? I'm gonna have to alarm Qmail-Scanner so it also spits the dummy before 20 minutes (I hope other MTAs don't have shorter timeouts). That way it'll always be telling the sender MTA it's in trouble. Another solution would be to just accept the message before scanning it, and scan it after the sending server has gone away - but then I'd have to write an entire requeuing infrastructure to handle transient errors too (not bl**dy likely ;-) Oh yeah - and please don't say "limit the size" - we LIKE sending large things here :-) [we just don't appear to like receiving them ;-)] Am I missing something here? This seems to imply that if you had /var/qmail/queue on a VERY slow (but otherwise reliable) disk, that you would see this problem too. I hope I'm just been stupid and missed something obvious... -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
[OT] Re: Sticky question about qmail-queue and qmail-smtpd interactions
Thus said Jason Haar on Fri, 20 Apr 2001 14:06:02 +1200: me to realise a rare error condition I hadn't expected. This virus scanner didn't like scanning a 90Mb zip'ped AVI file (ahem) - whereas another vendor scanner took 1.5minutes to scan it, this one took nearly two hours... Tell them to send MPEG instead. ;-) Andy -- [---[system uptime]] 8:23pm up 12 days, 23:39, 6 users, load average: 1.46, 1.50, 1.45
Re: Sticky question about qmail-queue and qmail-smtpd interactions
Solution, stop emailing yer smutty pr0n to everyone.
Re: Sticky question about qmail-queue and qmail-smtpd interactions
On Fri, Apr 20, 2001 at 02:06:02PM +1200, Jason Haar wrote: Hi there I'm the author of Qmail-Scanner - an Email scanning harness that can be used to block attachments, scan for viruses, etc. It's hooked in as a replacement for qmail-queue. The installation of a rather slow virus scanner on my own systems had lead me to realise a rare error condition I hadn't expected. This virus scanner didn't like scanning a 90Mb zip'ped AVI file (ahem) - whereas another vendor scanner took 1.5minutes to scan it, this one took nearly two hours... The sending SMTP server's qmail-remote timed out the SMTP session after 20 minutes - as being in error - as it had waited "too long" for the final "OK". However, STDOUT on the receiving box still received the "mail from|rcpt to" envelope headers, so after 2 hours Qmail-Scanner happily delivered it back to the real qmail-queue for real delivery. So let me get this right, what's happening is this: o the remote site is connecting to qmail-smtpd o qmail-smtpd is in turn invoking your replacement qmail-queue program called Qmail-Scanner o Qmail-Scanner is in turn invoking the real qmail-queue. Your problem arises when Qmail-Scanner (more correctly the scanner it invokes I guess) takes a long time to process the data. In fact longer than the SMTP timeout of the remote site. Then here's what happens: o the remote site times out and closes the socket thinking the email delivery has failed o meanwhile Qmail-Scanner et al are happily processing the email totally oblivious to the lost connection. Eventually the scan completes and the mail is injected into the local queue with qmail-queue. The key is that Qmail-Scanner doesn't know that the socket has been closed and that qmail-smtpd has exited. My suggestion is that you take a two-pronged approach. First off, introduce a timeout in Qmail-Scanner and exit accordingly (exit(52) according to the qmail-queue man page). Second off, I'd determine the process id of the parent with getppid() and at the point at which the scan is complete - but just prior to completing the qmail-queue - I'd use kill(parent, 0) to determine that qmail-smtpd is still around. All you are really doing is reducing the window of risk to a very small - but non-zero - size. But non-zero is ok as SMTP is idempotent. Your remaining problem is that the sender will never succeed as the mail is too large to process within their SMTP time-frame, so a better strategy might be to disconnect the scanner from SMTP. This is pretty trivial with a two-instance qmail install but it sure adds complexity for your customers. Regards. However... back on the sending host, it tried to send it again... I had a little loop going there - quite nasty. Can you say "busy system"? :-) Anyhoo, the virus scanner is the real culprit here - and that's something that can be fixed (i.e. get another). The problem is WHY did the recipient qmail-smtpd send through the envelope headers via STDOUT to qmail-queue/Qmail-Scanner? Upon noticing the sender going away, shouldn't it have recognised that as an error condition? I'm gonna have to alarm Qmail-Scanner so it also spits the dummy before 20 minutes (I hope other MTAs don't have shorter timeouts). That way it'll always be telling the sender MTA it's in trouble. Another solution would be to just accept the message before scanning it, and scan it after the sending server has gone away - but then I'd have to write an entire requeuing infrastructure to handle transient errors too (not bl**dy likely ;-) Oh yeah - and please don't say "limit the size" - we LIKE sending large things here :-) [we just don't appear to like receiving them ;-)] Am I missing something here? This seems to imply that if you had /var/qmail/queue on a VERY slow (but otherwise reliable) disk, that you would see this problem too. I hope I'm just been stupid and missed something obvious... -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
Re: Sticky question about qmail-queue and qmail-smtpd interactions
Spot on Mark, sounds like I'll alarm Q-S, and add your kill suggestion - that'll stop Q-S double-delivering if qmail-smtpd dies. On Fri, Apr 20, 2001 at 03:48:50AM +, Mark Delany wrote: All you are really doing is reducing the window of risk to a very small - but non-zero - size. But non-zero is ok as SMTP is idempotent. Yup - SMTP has always erred on the "duplicate-is-better-than-miss" side - fair enough too... Thanks for the ideas -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417
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.
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 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.
---
qmail-scanner handoff to qmail-queue not going well
One of my users has observed that mail addressed to him late at night seems to frequently get delayed. for very long periods of time. He sent me headers which look like this: Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: (qmail 19114 invoked from network); 9 Mar 2001 11:20:54 - Received: from hydepark-jump.vircio.com (qmailr@[10.1.1.1]) (envelope-sender [EMAIL PROTECTED]) by hackberry.vircio.com (qmail-ldap-1.03) with SMTP for [EMAIL PROTECTED]; 9 Mar 2001 11:20:54 - Received: (qmail 32510 invoked by uid 84); 9 Mar 2001 02:59:42 - Received: from [EMAIL PROTECTED] by hydepark-jump.vircio.com with qmail-scanner-0.90 (uvscan: v4.0.50/v4115. . Clean. Processed in 0.328525 secs); 08/03/2001 20:59:42 Received: from mailgate.1starnet.com (HELO mail.1starnet.com) ([207.243.104.248]) (envelope-sender [EMAIL PROTECTED])by cust-46-98.customer.jump.net (qmail-ldap-1.03) with SMTPfor [EMAIL PROTECTED]; 9 Mar 2001 02:59:41 - Received: from sweep2 [207.243.105.243] by mail.1starnet.com (SMTPD32-6.05) id A71C11570140; Thu, 08 Mar 2001 20:59:40 -0600 Received: (from default [12.41.197.55]) by sweep2 (NAVIEG 2.1 bld 63) with SMTP id M2001030820593623359for [EMAIL PROTECTED]; Thu, 08 Mar 2001 20:59:37 -0600 From: "Joan Heuston" [EMAIL PROTECTED] To: "David" [EMAIL PROTECTED] Subject: Trip Date: Thu, 8 Mar 2001 21:08:39 -0600 Message-ID: 01c0a846$3d8e7fe0$37c5290c@default MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_NextPart_000_0004_01C0A813.F2F40FE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 X-UID: 14 I ran them through a slightly modified version of the mailroute.pl script to see this: Thu Mar 8 2001 20:59:37 (from default [12.41.197.55]) by sweep2 (NAVIEG 2.1 bld 63) with SMTP id M2001030820593623359 for [EMAIL PROTECTED] 20:59:40 from sweep2 [207.243.105.243] by mail.1starnet.com (SMTPD32-6.05) id A71C11570140 20:59:41 from mailgate.1starnet.com (HELO mail.1starnet.com) ([207.243.104.248]) (envelope-sender [EMAIL PROTECTED]) by cust-46-98.customer.jump.net (qmail-ldap-1.03) with SMTP for [EMAIL PROTECTED] 20:59:42 from [EMAIL PROTECTED] by hydepark-jump.vircio.com with qmail-scanner-0.90 (uvscan: v4.0.50/v4115. . Clean. Processed in 0.328525 secs) 20:59:42 (qmail 32510 invoked by uid 84) Fri 9 05:20:54 from hydepark-jump.vircio.com (qmailr@[10.1.1.1]) (envelope-sender [EMAIL PROTECTED]) by hackberry.vircio.com (qmail-ldap-1.03) with SMTP for [EMAIL PROTECTED] 05:20:54 (qmail 19114 invoked from network) 2001-03-09 05:18:35.339952500 HydePark-Jump.virCIO.Com: new msg 50506 2001-03-09 05:18:35.475620500 HydePark-Jump.virCIO.Com: info msg 50506: bytes 4620 from [EMAIL PROTECTED] qp 32510 uid 84 2001-03-09 05:18:54.574282500 HydePark-Jump.virCIO.Com: starting delivery 542: msg 50506 to local [EMAIL PROTECTED] 2001-03-09 05:18:54.685686500 HydePark-Jump.virCIO.Com: delivery 542: success: did_0+0+0/ 2001-03-09 05:20:53.589986500 HydePark-Jump.virCIO.Com: starting delivery 895: msg 50506 to remote [EMAIL PROTECTED] 2001-03-09 05:20:54.606229500 HydePark-Jump.virCIO.Com: delivery 895: success: 10.1.1.5_accepted_message./Remote_host_said:_250_ok_984136854_qp_19114/ 2001-03-09 05:20:54.608846500 HydePark-Jump.virCIO.Com: end msg 50506 2001-03-09 05:20:59.447298500 Hackberry.virCIO.Com: new msg 22132 2001-03-09 05:20:59.447644500 Hackberry.virCIO.Com: info msg 22132: bytes 4911 from [EMAIL PROTECTED] qp 19114 uid 101 2001-03-09 05:21:02.173139500 Hackberry.virCIO.Com: starting delivery 644: msg 22132 to local [EMAIL PROTECTED] 2001-03-09 05:21:02.210565500 Hackberry.virCIO.Com: starting delivery 645: msg 22132 to local [EMAIL PROTECTED] 2001-03-09 05:21:03.041980500 Hackberry.virCIO.Com: delivery 644: success: did_0+0+0/ 2001-03-09 05:21:03.098023500 Hackberry.virCIO.Com: delivery 645: success: did_1+0+0/ 2001-03-09 05:21:03.437875500 Hackberry.virCIO.Com: end msg 22132 This afternoon's hackery was to extract my hostname from the headers and grovel through the logs to find the info you see at the bottom. Anyway, as you can see, qmail-scanner appears to have handed the message off to qmail-queue at Thu Mar 8 2001 20:59:42 according to the headers, but it doesn't show up in the logs until 2001-03-09 05:18:35.339952500. I'm very confused here. It is true that qmail-queue adds the (qmail 32510 invoked by uid 84) line, right? How can it possibly not log it until so many hours later? I have a job that kicks
Qmail Queue is out of control ....
Hi everyone, 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. Thank you for your help
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. ---
qmail-queue problems
Hi folks, I have a single qmail-queue process that is eating all of my resources. I have used the queue-fix program in test mode and it has not found any problems. When I run the utility to list the queue, there are only about 20 messages in and all have been preproccessed. I am currently searching the archives for answers, but if anyone has tackled this issue in the past, I would appreciate your input. Thanks, Chris
QMAIL- QUEUE FILE SYSTEM FULL
Hi, 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. Raghu
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: How can I delete all unsended mails in /var/qmail/queue?
[EMAIL PROTECTED] wrote: There are so many garbage mails in /var/qmail/queue. Is there a good and simple way to delete all mails in the queue? Can I use OS commands as "mv" or "rm" ? Sure. See: http://www.faqts.com/knowledge_base/view.phtml/aid/6567/fid/286 -Dave
How can I delete all unsended mails in /var/qmail/queue?
There are so many garbage mails in /var/qmail/queue. Is there a good and simple way to delete all mails in the queue? Can I use OS commands as "mv" or "rm" ? Thanks. -- »¶ÓʹÓà 21CN µç×ÓÓʼþϵͳ http://www.21cn.com Thank you for using 21cn.com Email system
Re: How can I delete all unsended mails in /var/qmail/queue?
On Mon, Feb 05, 2001 at 12:41:20AM +0800, [EMAIL PROTECTED] wrote: There are so many garbage mails in /var/qmail/queue. Is there a good and simple way to delete all mails in the queue? Can I use OS commands as "mv" or "rm" ? Sure. Here they are: 1. # Stop qmail 2. # rm -rf /var/qmail/queue 3. # cd qmail-sources 4. # make setup check 5. # Start qmail Regards.
Clean out /var/qmail/queue/pid + send automatic reply
Hi, I'm a newbie qmail admin getting more and more enthousiastic about this MTA, even though I've just spent some time troubleshooting my first qmail problem after someone accidentally deleted a qmail user account and changed permissions on some directories. My mail system was suffering from a "451 qq trouble creating files in queue (#4.3.0)" message when receiving/trying to queue mail. I found a lot of people asking what this was all about all over the net, but no real solution to the problem. Well, I just want to add my own 0.02 $ by saying that it's all permissions and owner-related. I found the "make check" (which calls instcheck) from the build directory to be the most effective tool to find out where file ownerships and permissions have gone berserk. Note that usernames don't really matter for qmail, it's the userids that have to match ! Recreating a deleted account with a different userid doesn't solve things, you have to change the uid in /etc/passwd afterwards. I have two quick questions though: How can I clean out /var/qmail/queue/pid after an ungraceful shutduwn ? (you've guessed it, at some point I thought it would be useful to just kill -9 all qmail processes) I have no idea which files shouldn't be in that folder. [root@yuclnx1 queue-fix-1.4]# /var/qmail/bin/instcheck [root@yuclnx1 queue-fix-1.4]# /var/qmail/bin/qmail-lint [root@yuclnx1 queue-fix-1.4]# /var/qmail/bin/qmail-qsanity [root@yuclnx1 queue-fix-1.4]# /var/qmail/bin/queue-fix -N /var/qmail/queue/ Running in test mode, no changes will be made. Found files in /var/qmail/queue/pid that shouldn't be there. I will not remove them. You should consider checking it out. queue-fix finished... How do I find out what files to delete ? There are 151 files in the folder. Also, due to a domain name change, I need to implement the following: all people sending mail to [EMAIL PROTECTED] should receive a reply saying that they should now use [EMAIL PROTECTED] I know it shouldn't be too difficult to redirect mail from @subdomain.domain.com to @domain.com, but our management really wants to have automated replies to the senders... Regards, Filip
Re: Clean out /var/qmail/queue/pid + send automatic reply
On Wed, Jan 31, 2001 at 11:22:32AM +0100, Filip Sneppe (Yucom) wrote: [snip] How can I clean out /var/qmail/queue/pid after an ungraceful shutduwn ? (you've guessed it, at some point I thought it would be useful to just kill -9 all qmail processes) I have no idea which files shouldn't be in that folder. Any garbage in the queue will get removed after 36 hours, if I'm correct. [snip] Also, due to a domain name change, I need to implement the following: all people sending mail to [EMAIL PROTECTED] should receive a reply saying that they should now use [EMAIL PROTECTED] I know it shouldn't be too difficult to redirect mail from @subdomain.domain.com to @domain.com, but our management really wants to have automated replies to the senders... Uh, put subdomain.domain.com:alias-moved into virtualdomains then create ~alias/.qmail-moved-default, containing |bouncesaying 'this domain has moved to domain.com' Disclaimer: I got out of bed 2 minutes ago and may be saying very stupid things :) Greetz, Peter
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
qmail queue problems .. help
hi all !i'm wondering if exists some binaries or scripts to cleanup/fixthe qmail queue( /opt/qmail/queue/mess /remote /info /bounce)because i got error messages in logs like :"cannot stat mess/[message N°]""cannot open message" will try again later"when i run /opt/qmail/bin/qmail-qstat, i always have about 1000 messages in queue i'm also receiving messages from foreign hosts about outgoing messages bouncing from my server ...thx for help. José CarreiroURBANET S.AVallombreuse 511000 Lausanne 22http://www.urbanet.ch
Re: Using a RAMDISK for /var/qmail/queue thoughts ?
David Dyer-Bennet wrote: Um, most reporting measured results from optimizing high-traffic qmail-based mail servers have found that disk activity on the queue disk is the first limit they hit. How about, if the first delivery fails, pass it off to a server with some disks. Why not pre-process with qmail-remote before queueing? -- David Nicol 816.235.1187 [EMAIL PROTECTED] Five seconds of light is a lot of data.
Re: Using a RAMDISK for /var/qmail/queue thoughts ?
On Fri, Jan 26, 2001 at 05:46:51PM -0600, David L. Nicol wrote: David Dyer-Bennet wrote: Um, most reporting measured results from optimizing high-traffic qmail-based mail servers have found that disk activity on the queue disk is the first limit they hit. How about, if the first delivery fails, pass it off to a server with some disks. Why not pre-process with qmail-remote before queueing? qmail-remote is way too late as most of the I/O load is putting the mail in the queue, not getting it off. Besides, the symptom isn't delivery failure, it's slowness. Regards.
Re: Using a RAMDISK for /var/qmail/queue thoughts ?
On Fri, Jan 26, 2001 at 11:56:54PM +, Mark Delany wrote: On Fri, Jan 26, 2001 at 05:46:51PM -0600, David L. Nicol wrote: David Dyer-Bennet wrote: Um, most reporting measured results from optimizing high-traffic qmail-based mail servers have found that disk activity on the queue disk is the first limit they hit. How about, if the first delivery fails, pass it off to a server with some disks. Why not pre-process with qmail-remote before queueing? qmail-remote is way too late as most of the I/O load is putting the mail in the queue, not getting it off. Besides, the symptom isn't delivery failure, it's slowness. Actually. I was little hasty on the first point. I now see what you're getting at. One question is, how far do you let qmail-remote go before deciding it will work. It it's past the MAIL FROM/RCPT TO part, then why not complete the delivery rather than incur the double load and double latency? If you mean to try and completely do the remote delivery prior to placing it in the queue, then this is the passthru idea that people have suggest previously. It potentially has merit with an amount of added complexity. One problem is that a busy system, such as a mailing list system may be at full concurrencyremote for extended periods of time, in which case, new submissions should not attempt qmail-remote delivery so you're back to square one. Another problem is that the mail has to be stored somewhere while qmail-remote attempts delivery. Well, unless you want the submitting client to wait - that may create a lot of confusing latency for, eg, people sitting on a PC using Eudora. If the mail is stored somewhere, you're starting to get back to a disk queue. But it's not necessarily a silly idea. I believe that sendmail tries to do something like this in certain circumstances. A monolithic design has an advantage in this regard. Doing this is a nice compartmentalized way with the current qmail wouldn't be a lot of fun. Regards.
qmail-queue
Hi, Can you send me a qmail-queue patched for use with qmail-scanner, because i have patched qmail-queue but the 2 files have the same size ! Thanks Nicolas DEFFAYET, NDSoftware http://www.ndsoftware.net - [EMAIL PROTECTED] France: Tel +33 671887502 - Fax N/A UK: Tel +44 8453348750 - Fax +44 8453348751 USA: Tel N/A - Fax N/A
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
QMail Queue
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. Thanks Nicolas DEFFAYET, NDSoftware http://www.ndsoftware.net - [EMAIL PROTECTED] France: Tel +33 671887502 - Fax N/A UK: Tel +44 8453348750 - Fax +44 8453348751 USA: Tel N/A - Fax N/A
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
sendmail to qmail queue transfer
Dear All I have two mailq's, the primary is running sendmail v8 the secondary isrunning qmail 1.03.I have just finished configuring a replacement for the new primary whichwill also be running qmail 1.03. Where I need advice is how best to make the swap and how best to flush the queue on the old box into the new.I had thought of the following;1:) drop the queue lifetime down on the primary sendmail boxto nearing 72hrs (shorter than the RFC advised 120 hrs) to keep the queue assmall as possible.2:) remove the primary mailq, domain mail would then take the next best mxpref and head for the secondary mailq and queue their.3:) reconfig the old primary (sendmail) with a temporary hostname and IP onthe server network.4:) install the new primary mailq (qmail) which of course would startaccepting mail the moment the smtpd daemon is up.NOW the bit thats bothering me.5:) would the secondary after 60 mins (or send qmail-send an svc -a alarm) then deliver its queue back to the new mailq as it has a lower mx?6:) would the old reconfigured sendmail also deliver its queue to the newmailq as DNS would give that as the lowest mx pref. All assume the final destination is a MTA on a dial up.Many thanks in advance. Mike[EMAIL PROTECTED]
sendmail to qmail queue transfer (txt)
Dear All I have two mailq's, the primary is running sendmail v8 the secondary is running qmail 1.03. I have just finished configuring a replacement for the new primary which will also be running qmail 1.03. Where I need advice is how best to make the swap and how best to flush the queue on the old box into the new. I had thought of the following; 1:) drop the queue lifetime down on the primary sendmail box to nearing 72hrs (shorter than the RFC advised 120 hrs) to keep the queue as small as possible. 2:) remove the primary mailq, domain mail would then take the next best mx pref and head for the secondary mailq and queue their. 3:) reconfig the old primary (sendmail) with a temporary hostname and IP on the server network. 4:) install the new primary mailq (qmail) which of course would start accepting mail the moment the smtpd daemon is up. NOW the bit thats bothering me. 5:) would the secondary after 60 mins (or send qmail-send an svc -a alarm) then deliver its queue back to the new mailq as it has a lower mx? 6:) would the old reconfigured sendmail also deliver its queue to the new mailq as DNS would give that as the lowest mx pref. All assume the final destination is a MTA on a dial up. Many thanks in advance. Mike [EMAIL PROTECTED]
