Re: script filter before qmail-local .. solved
Ok, just in case anybody else will fight with it too, I found this: seekablepipe http://www.skarnet.org/software/qmail-local-mda/ -- jozef :-)
script filter before qmail-local
Hi, I'm quite sure this is near FAQ, but I didn't succeed trying guessing it myself, nor looking through archives, so pls forgive my asking here - What I'm trying to do, is put a perl filter just before qmail-local puts its hands on mail. I moved qmail-local to qmail-local-orig and put in a script named qmail-local, which calls the filter first. Could you please tell me if it is possible to do this with a sh or perl script? If yes, any hint will be highly appreciated, an example of script which just does nothing and forwards mail to qmail-local-orig would be great. I know I could write qmail-local replacement in C (qmail-lspawn.c qmail-local.c as inspiration), but I'd prefer the script solution now, if possible. The resulting flow would be like this: qmail-lspawn --origmsg- qmail-local --filteredmsg- qmail-local-orig The filter itself is simple one-pass always-success script, which just scans attachements for .exe, .vbs, .. and adds .VIRUS extension, so that nobody can simply click through the worms (yes I have such users here). Yes, I'll make the script available (BSD) after some more testing. Thanks, -- jozef :-)
Don't understand qmail-local parameter!!!
Hell all: The qmail-local usage is: usage: qmail-local [ -nN ] user homedir local dash ext domain sender aliasempty.But can't understand every parameter meaning except user,homedir,domain. Anyone can help me to undrstand? Thanks!
Re: Don't understand qmail-local parameter!!!
hi, man qmail-local NAME qmail-local - deliver or forward a mail message SYNOPSIS qmail-local [ -nN ] user homedir local dash ext domain sender defaultdelivery DESCRIPTION qmail-local reads a mail message and delivers it to user by the procedure described in dot-qmail(5). The message's envelope recipient is local@domain. qmail- local records local@domain in a new Delivered-To header field. If exactly the same Delivered-To: local@domain already appears in the header, qmail-local bounces the message, to prevent mail forwarding loops. The message's envelope sender is sender. qmail-local records sender in a new Return-Path header field. homedir is the user's home directory. It must be an abso- lute directory name. dash and ext identify the .qmaildashext file used by qmail-local; see dot-qmail(5). Normally dash is either empty or a lone hyphen. If it is empty, qmail-local treats a nonexistent .qmailext the same way as an empty .qmailext: namely, following the delivery instructions in defaultdelivery. The standard input for qmail-local must be a seekable file, so that qmail-local can read it more than once. OPTIONS -n Instead of reading and delivering the message, print a description of the delivery instructions. -N (Default.) Read and deliver the message. - from man qmail-local--- Regards Santosh Pasi ---Original Message-- Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk Date: Wed, 30 May 2001 14:38:47 +0800 From: george [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Don't understand qmail-local parameter!!! Content-Transfer-Encoding: 7bit Hell all: The qmail-local usage is: usage: qmail-local [ -nN ] user homedir local dash ext domain sender aliasempty.But can't understand every parameter meaning except user,homedir,domain. Anyone can help me to undrstand? Thanks!
Re: Don't understand qmail-local parameter!!!
The qmail-local usage is:" usage: qmail-local [ -nN ] user homedir local dash ext domain sender aliasempty".But can't understand every parameter meaning except user,homedir,domain. Anyone can help me to undrstand? 'man qmail-local' will help you much. B.Csaba __ This message went through virus scan at Trend Ltd. which stated the message was clean of viri appeared before 2001.05.24.
Re: Don't understand qmail-local parameter!!!
On Wed, May 30, 2001 at 02:38:47PM +0800, george wrote: Hell all: The qmail-local usage is: usage: qmail-local [ -nN ] user homedir local dash ext domain sender aliasempty.But can't understand every parameter meaning except user,homedir,domain. Anyone can help me to undrstand? There is no need to use qmail-local directly. qmail-send handles this for you. Stop worrying. Greetz, Peter.
Re: Don't understand qmail-local parameter!!!
On Wed, May 30, 2001 at 12:27:02PM +0530, Santosh Pasi wrote: hi, man qmail-local [snip qmail-local manpage] - from man qmail-local--- That was completely uncalled for and a waste of bandwidth. Greetz, Peter.
qmail-lspawn / qmail-local
Hi all, 1. I need to get qmail-lspawn to deliver into /var/qmail/alias/local/Maildir/new/ 2. My footer program will identify the type of message, add the appropricate footer and feed the mail into /var/qmail/alias/local.footer/Maildir/new/ 3. I need next to feed the mail from /var/qmail/alias/local.footer/Maildir/new/ into qmail-local for local delevery. Step 2 works quite ok on my remote mail, What I need help with is step 1 and step 3. It might also be an idea to change qmail-lspawn to be some kind of wrapper, and feed into the real qmail-lspawn. Help is much appriciated thanks in advance Mettavihari Sri Lanka. A saying of the Buddha from http://metta.lk/ He who wholly subdues evil deeds both small and great, is called a monk because he has overcome all evil. Random Dhammapada Verse 265
error with qmail-local
Hi. I've recently installed Qmail 1.03 on a Suse 7.1 linux server, and after the initial setup (not using tcpserver) I could run and access and deliver mail normally. After setting up tcpserver and getting it running and working however, my SMTP server continues to receive and que mail, but will no longer deliver it. When I run qmail-local manually it returns a Error 4.3.0: Unable to Rewind Message error. Thoughts help or suggestions would be GREATLY appreciated.
Re: qmail-inject refuses to work if it's parent process is qmail-local?
On Fri, Feb 16, 2001 at 05:34:03PM -0800, David Cunningham wrote: Thank you Charles. I'll be sure to look at that. The goal here is not so much to get a functional autoresponder as it is to satisfy my curiosity about the behavior of qmail in terms of script processing. I tested a .qmail file with: |/var/qmail/bin/qmail-inject [EMAIL PROTECTED] and it worked just fine. Why do you need perl? Starting it, writing a file and then starting qmail-inject is rather expensive. Regards, james -- James Raftery (JBR54) "It's somewhere in the Red Hat district" -- A network engineer's freudian slip when talking about Amsterdam's nightlife at RIPE 38.
Re: qmail-inject refuses to work if it's parent process is qmail-local?
James Raftery [EMAIL PROTECTED] wrote: I tested a .qmail file with: |/var/qmail/bin/qmail-inject [EMAIL PROTECTED] and it worked just fine. Why do you need perl? Starting it, writing a file and then starting qmail-inject is rather expensive. If it comes down to that, why not: [EMAIL PROTECTED] 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-inject refuses to work if it's parent process is qmail-local?
David Cunningham [EMAIL PROTECTED] wrote: Thank you Charles. I'll be sure to look at that. The goal here is not so much to get a functional autoresponder as it is to satisfy my curiosity about the behavior of qmail in terms of script processing. Ah, well that's a totally different story then. The man pages for dot-qmail and qmail-command will be of particular interest. 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. ---
scripting problems with qmail-inject and qmail-local
I'm trying to write a script that will watch for incoming mail and send out a response when one arrives. I've tried to spawn the script from .qmail but it appears that qmail-inject refuses to accept input from my script when the script is ran by qmail-local. Any suggestions for how to write a script to get around this problem?
Re: scripting problems with qmail-inject and qmail-local
On Fri, Feb 16, 2001 at 03:49:24AM -0800, David Cunningham wrote: I'm trying to write a script that will watch for incoming mail and send out a response when one arrives. I've tried to spawn the script from .qmail but it appears that qmail-inject refuses to accept input from my script when the script is ran by qmail-local. Please define "refuses". Doesn't execute? Gives an error? Siliently discards mail? Any suggestions for how to write a script to get around this problem? Use one of the auto-responders on http://www.qmail.org/top.html? james -- James Raftery (JBR54) "It's somewhere in the Red Hat district" -- A network engineer's freudian slip when talking about Amsterdam's nightlife at RIPE 38.
qmail-inject refuses to work if it's parent process is qmail-local?
I'm trying to write a script that sends out a reply email when someone send
email to a certain address in my domain. The idea is someone sends mail to
[EMAIL PROTECTED] and a generic message is sent back to them. So far I
can't get anything sent anywhere if I let qmail-local run the program.
Here's the details:
/home/radius/.qmail-info contains:
|/home/radius/replyscript.pl
The replyscript.pl contains:
#!/usr/bin/perl
system ("cat message /tmp/message");
system ("/var/qmail/bin/qmail-inject message");
exit 0;
And /home/radius/message contains:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Did it work?
Test
If I send mail to [EMAIL PROTECTED] the script will copy the message to the
/tmp directory. This tells me that the script does in fact execute and the
file /home/radius/message is in the present working directory. However when
the script attempts to send the message to qmail-inject, the following error
is logged:
qmail-inject:_fatal:_read_error/did_0+0+1/
If I log into the Linux box and run the script directly it works fine. It
seems as if qmail-inject refuses to work if it's parent process is
qmail-local. Is this true? Know of any workarounds?
|/\\/||
Re: qmail-inject refuses to work if it's parent process is qmail-local?
David Cunningham [EMAIL PROTECTED] wrote: I'm trying to write a script that sends out a reply email when someone send email to a certain address in my domain. You don't need to re-invent the wheel. There's also many things your script doesn't consider (not responding to other autoresponders, not responding to bounces, etc). Just look for "autoresponder" on www.qmail.org and you'll find some examples from people who have considered these issues. 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-inject refuses to work if it's parent process is qmail-local?
Thank you Charles. I'll be sure to look at that. The goal here is not so much to get a functional autoresponder as it is to satisfy my curiosity about the behavior of qmail in terms of script processing. I like to "re-invent the wheel" because it gives me insights I wouldn't have otherwise. -David - Original Message - From: "Charles Cazabon" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 16, 2001 5:10 PM Subject: Re: qmail-inject refuses to work if it's parent process is qmail-local? David Cunningham [EMAIL PROTECTED] wrote: I'm trying to write a script that sends out a reply email when someone send email to a certain address in my domain. You don't need to re-invent the wheel. There's also many things your script doesn't consider (not responding to other autoresponders, not responding to bounces, etc). Just look for "autoresponder" on www.qmail.org and you'll find some examples from people who have considered these issues. 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: Local users can clog qmail local queue
Has this been a problem for anyone in practice? It appears to constitute a security problem that a single local user can shut down all local mail delivery indefinitely. In theory, you are correct, although this is a Denial-Of-Service attack rather than a strict security breach. In practice, a local user has many other avenues of attack similar to this, and for all of them the fix is quite simply to throw the user off the system. If you run a system with users you worry about, you can (IIRC) use /var/qmail/users/assign to disallow them from using their .qmail file. Consider instead a user who puts a stupid filter in his .qmail that will execute commands listed in an email with COMMAND as the subject line. NOW you have a real security hole. -- gowen -- Greg Owen -- [EMAIL PROTECTED] SoftLock.com is now DigitalGoods!
Re: Local users can clog qmail local queue
On Wed, Jan 03, 2001 at 12:52:49PM -0500, Greg Owen wrote: In theory, you are correct, although this is a Denial-Of-Service attack rather than a strict security breach. In practice, a local user has many other avenues of attack similar to this, and for all of them the fix is quite simply to throw the user off Yes; definitely. There's nothing special about local users (though they do have more potential for mischief). A local or remote user could give you a large email to be delivered to a slow remote mail server which, if send enough times, can use up all your remote delivery slots and 'clog the remote queue'. Such is life. Analyse your logs. Watch your local/remote concurrency. Wield a big stick. james -- James Raftery (JBR54) "Managing 4000 customer domains with BIND has been a lot like herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
Re: Local users can clog qmail local queue
Greg Owen wrote: Consider instead a user who puts a stupid filter in his .qmail that will execute commands listed in an email with COMMAND as the subject line. NOW you have a real security hole. ...which is why .qmail commands are executed as the user, instead of as root or as one of the qmail users. Assuming you don't have any other local holes, the worst that user can do is machine gun himself in the foot, and he doesn't need qmail to do that! ---Kris
RE: Local users can clog qmail local queue
...which is why .qmail commands are executed as the user, instead of as root or as one of the qmail users. Assuming you don't have any other local holes, the worst that user can do is machine gun himself in the foot, and he doesn't need qmail to do that! ...you should always assume you have local holes. Even if you don't, allowing random remote people to get commands executed as local users is a problem - how about '/bin/mail [EMAIL PROTECTED] /etc/passwd'? Even if there's a shadow file, that'll list usernames to guess passwords on. But, more to the point, check out http://cr.yp.to/qmail/guarantee.html: "Of course, ``security hole in qmail'' does not include problems outside of qmail: for example, NFS security problems, TCP/IP security problems, DNS security problems, bugs in scripts run from .forward files, and operating system bugs generally. It's silly to blame a problem on qmail if the system was already vulnerable before qmail was installed! I also specifically disallowed denial-of-service attacks: they are present in every MTA, widely documented, and very hard to fix without a massive overhaul of several major protocols. (UNIX does offer some tools to prevent local denial-of-service attacks; see my resource exhaustion page for more information.)" -- gowen -- Greg Owen -- [EMAIL PROTECTED] SoftLock.com is now DigitalGoods!
Re: Local users can clog qmail local queue
On Wed, Jan 03, 2001 at 12:39:43PM -0500, Mark-Jason Dominus wrote: A local user, eric, can set up .qmail-slow like this: | sleep 3600 If Eric then sends a few hundred pieces of mail to eric-slow, qmail's local queue will fill up, and local mail delivery will be stopped. Incoming mail will not be delivered until Eric's 'sleep' processes time out. Has this been a problem for anyone in practice? It appears to constitute a security problem that a single local user can shut down all local mail delivery indefinitely. Surprise surprise, this is not the first time this issue has been raised. A simple suggestion in 1998 was to have a timeout on qmail-local deliveries. See: http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/02/msg00662.html Regards.
Re: Local users can clog qmail local queue
Says "Mark Delany" [EMAIL PROTECTED]: http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/02/msg00662.html The 1998 discussion was just what I was looking for. (I searched for something like that before I sent my message, but didn't find it.) Specifically, I was wondering about the feasibilty of a per-user concurrency limit, but the archived discussion points out that it is probably a bad idea. The discussion also mentions the possibiliy of a timeout in qmail-local, but that also appears to be a good idea. Thanks very much.
RE: Qmail local question
This is a better question for the vpopmail list [EMAIL PROTECTED] -Original Message- From: eddy [mailto:eddy]On Behalf Of Eddy Fafard Sent: Thursday, December 21, 2000 6:22 PM To: [EMAIL PROTECTED] Subject: Qmail local question Qmail with Vpopmail We are currently transitining from Sendmail to Qmail for our main mail server. So we have some users on this new server, and the rest on the old server. Our relays point to the old server and aliases directs qmail users mail to the Qmail server. Problem is: when Qmail users send mail to users on the old servers it trys to deliver it locally and when the user and dumps it in postmaster mailbox. All worked fine as of yesterday but now it does not work. The domain is not in /var/qmail/locals and my mx records look fine. Any ideas ? Here is the error from the maillog, user is not in the qmail server but try to delive it anyway .. Dec 21 15:14:52 mail-1 qmail: 977440492.682140 starting delivery 6: msg 3244038 to local [EMAIL PROTECTED] Dec 21 15:14:52 mail-1 qmail: 977440492.682279 status: local 1/10 remote 0/20 Dec 21 15:14:52 mail-1 tcpserver: 977440492.699820 tcpserver: end 1892 status 0 Dec 21 15:14:52 mail-1 tcpserver: 977440492.700093 tcpserver: status: 0/20 Dec 21 15:14:52 mail-1 qmail: 977440492.700794 delivery 6: success: POP_user_does_not_exist,_but_will_deliver_to_/var/vpopmail/domains/iescrow.c om/postmaster/
qmail-local killed
Hi, My redhat6.2 + qmail(rpm) box was panic and I saw this line in syslog. Oct 10 15:36:12 member kernel: Bad pmd in pte_alloc: 448b5008 Oct 10 15:36:12 member kernel: VM: killing process qmail-local Oct 10 15:36:12 member kernel: Unable to handle kernel paging request at virtual address 1309a3ce Oct 10 15:36:12 member kernel: current-tss.cr3 = 154ea000, %cr3 = 154ea000 Oct 10 15:36:12 member kernel: *pde = Oct 10 15:36:12 member kernel: Oops: 0002 Oct 10 15:36:12 member kernel: CPU:0 Oct 10 15:36:12 member kernel: EIP:0010:[move_addr_to_kernel+30/56] Oct 10 15:36:12 member kernel: EFLAGS: 00010202 Oct 10 15:36:12 member kernel: eax: 1309a3ce ebx: cddcdf6c ecx: d8b43f10 edx: 0003 Oct 10 15:36:12 member kernel: esi: d8b43f14 edi: 006e ebp: ba6c esp: d8b43ef8 Oct 10 15:36:12 member kernel: ds: 0018 es: 0018 ss: 0018 Oct 10 15:36:12 member kernel: Process ls (pid: 23074, process nr: 145, stackpage=d8b43000) Oct 10 15:36:12 member kernel: Stack: b9fc 006e d8b43f14 0002 0003 4010cd60 02a8 Oct 10 15:36:12 member kernel:cddcdf6c c6a17a00 c0173a14 c0173a74 0282 cddcded0 Oct 10 15:36:12 member kernel:c01308a0 df4ca800 c01df0a4 0001 cddcded0 df4ca7a0 cddcded0 Oct 10 15:36:12 member kernel: Call Trace: [unix_create1+60/163] [unix_create1+156/163] [d_alloc+110/279][cprt+388/23488] [d_alloc_root+49/57] [get_fd+53/147] [sys_socket+51/115] Oct 10 15:36:12 member kernel:[sys_socketcall+130/440] [error_code+45/52] [system_call+52/56] Oct 10 15:36:12 member kernel: Code: 10 00 24 14 50 e8 0d b7 08 00 83 c4 0c 85 c0 74 06 b8 f2 ff What should I do ? It happen 2 times a month. Do I have a problem with my RAM ? (I use 512Mb) I also got this from the syslog.please help me. Oct 10 22:10:18 member kernel: Uhhuh. NMI received. Dazed and confused, but trying to continue Oct 10 22:10:18 member kernel: You probably have a hardware problem with your RAM chips Joomy.
Re: qmail-local killed
"Joomy" == Joomy Studio [EMAIL PROTECTED] writes: Joomy Oct 10 22:10:18 member kernel: Uhhuh. NMI received. Dazed and Joomy confused, but trying to continue Joomy Oct 10 22:10:18 member kernel: You probably have a hardware Joomy problem with your RAM chips I'd say this is a pretty good explanation of your problems... Try pulling a ram chip for a fortnight. If it happens again, pull the next one. Keep doing this until you find the right one (or if you have money just go buy another 512mb). I have had similar troubles (machine crashing) because of faulty ram. Buying new ram fixed it on the spot. Good luck~ -- "I'm not dumb. I just have a command of throughly useless information." - Calvin, of Calvin and Hobbes
Qmail local spawn problems
Hi, I have some problems usingqmail 1.03 with mysql-patch 0.6.6 over Redhat 6.2. Pop3 service works fine, but qmail-getpw never gets executed and all local messages get lost. If I use users/assign works fine, but I need qmail-getpw working. I think that the problem is related to qmail-lspawn, but I`ve recompiled the source code more than once and it doesn't work. If by any chanceanyone could help me it would be great.
Re: qmail-lspawn to qmail-local strangeness
On Wed, Jun 28, 2000 at 07:43:08AM +0200, clemensF wrote: Ben Giddings: (As an aside, qmail looks like a great, highly flexible program, but man the source needs work. Virtually no comments anywhere, meaningless variable and function names. Not a fun thing to search through when you're trying to figure something out.) i give stags a few seconds and then browse through the sources without problems. i think they are a delight to read! I agree, I am not even a programmer (unless you count bash) and I am generally able to easily read through the source and find the part I need. --Adam
qmail-lspawn to qmail-local strangeness
Hey Everyone, I've been trying to get qmail to work for a few days, and have had almost no luck. Local delivery just doesn't work. When I do the local to local test the message bounces and eventually goes to the ~alias/Mailbox (postmaster) location. I've been trying to trace the problem for a while and I think I know what it is. It looks like qmail-lspawn is starting qmail-local with a dash as the "dash" argument. Because of this it is never even trying to put the mail in "Mailbox" in my home directory, instead it's just checking the .qmail-X files and when they're not found it's bouncing the mail. Now the local to local picture shows qmail-local being started with the dash and ext being both unset. The only time that doesn't appear to be the case is when there's a dash in the username part of the email address. Since this isn't the case, what's going on? (As an aside, qmail looks like a great, highly flexible program, but man the source needs work. Virtually no comments anywhere, meaningless variable and function names. Not a fun thing to search through when you're trying to figure something out.) Ben
Re: qmail-lspawn to qmail-local strangeness
Ben Giddings [EMAIL PROTECTED] wrote: I've been trying to get qmail to work for a few days, and have had almost no luck. Local delivery just doesn't work. When I do the local to local test the message bounces and eventually goes to the ~alias/Mailbox (postmaster) location. From http://Web.InfoAve.Net/~dsill/lwq.html#qmail-list: When you ask questions, please try to include sufficient details to make it possible for people to respond: What did you do? What's your configuration? Include qmail-showctl output if you're not sure what's important. What action did you take? What did you expect to happen? What was the outcome you were trying to achieve? Don't assume the reader can guess. What did happen? Describe the actual result. Include log file clippings and copies of messages, with headers. -Dave
Re: qmail-lspawn to qmail-local strangeness
Ben Giddings: (As an aside, qmail looks like a great, highly flexible program, but man the source needs work. Virtually no comments anywhere, meaningless variable and function names. Not a fun thing to search through when you're trying to figure something out.) i give stags a few seconds and then browse through the sources without problems. i think they are a delight to read! clemens
Re[2]: qmail-lspawn to qmail-local strangeness
Hey Dave, Tuesday, June 27, 2000, 2:38:07 PM, you wrote: DS When you ask questions, please try to include sufficient details to DS make it possible for people to respond: Sorry, I thought I had given enough information. Here's more: I test local delivery using my username: [Merc@linxsvr qmail]$ echo To: Merc | /var/qmail/bin/qmail-inject Nothing arrives in my mailbox, the logs show: Jun 28 01:33:05 linxsvr qmail: 962170385.298731 new msg 20095 Jun 28 01:33:05 linxsvr qmail: 962170385.300780 info msg 20095: bytes 263 from [EMAIL PROTECTED] qp 781 uid 500 Jun 28 01:33:05 linxsvr qmail: 962170385.357168 starting delivery 12: msg 20095 to local [EMAIL PROTECTED] Jun 28 01:33:05 linxsvr qmail: 962170385.358931 status: local 1/10 remote 0/20 Jun 28 01:33:05 linxsvr qmail: 962170385.398168 delivery 12: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ Jun 28 01:33:05 linxsvr qmail: 962170385.401041 status: local 0/10 remote 0/20 Jun 28 01:33:05 linxsvr qmail: 962170385.440118 bounce msg 20095 qp 784 Jun 28 01:33:05 linxsvr qmail: 962170385.441476 end msg 20095 Jun 28 01:33:05 linxsvr qmail: 962170385.506854 new msg 20096 Jun 28 01:33:05 linxsvr qmail: 962170385.509020 info msg 20096: bytes 896 from qp 784 uid 508 Jun 28 01:33:05 linxsvr qmail: 962170385.566720 starting delivery 13: msg 20096 to local [EMAIL PROTECTED] Jun 28 01:33:05 linxsvr qmail: 962170385.568202 status: local 1/10 remote 0/20 Jun 28 01:33:05 linxsvr qmail: 962170385.607263 delivery 13: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ Jun 28 01:33:05 linxsvr qmail: 962170385.610170 status: local 0/10 remote 0/20 Jun 28 01:33:05 linxsvr qmail: 962170385.648454 bounce msg 20096 qp 787 Jun 28 01:33:05 linxsvr qmail: 962170385.649828 end msg 20096 Jun 28 01:33:05 linxsvr qmail: 962170385.651847 new msg 20095 Jun 28 01:33:05 linxsvr qmail: 962170385.653327 info msg 20095: bytes 1427 from #@[] qp 787 uid 508 Jun 28 01:33:05 linxsvr qmail: 962170385.707588 starting delivery 14: msg 20095 to local [EMAIL PROTECTED] Jun 28 01:33:05 linxsvr qmail: 962170385.708518 status: local 1/10 remote 0/20 Jun 28 01:33:05 linxsvr qmail: 962170385.746751 delivery 14: deferral: Unable_to_open_./Mailbox:_access_denied._(#4.2.1)/ Jun 28 01:33:05 linxsvr qmail: 962170385.747755 status: local 0/10 remote 0/20 control/defaultdomain is X.com control/locals contains YYY.X.com (among others) control/me is YYY.X.com control/plusdomain is X.com control/rcpthosts is empty And ~alias looks like: [root@linxsvr qmail]# ls -la alias drwxr-sr-x4 aliasqmail1024 Jun 27 08:31 . drwxr-xr-x 12 root qmail1024 Jun 28 01:38 .. -rw-r--r--1 root 501 0 Jun 25 23:53 .qmail-mailer-daemon -rw-r--r--1 root 501 0 Jun 25 23:53 .qmail-postmaster -rw-r--r--1 root 501 0 Jun 25 23:53 .qmail-root -rw---1 103 501 20517 Jun 27 00:58 Mailbox Again, the problem seems to be that qmail_lspawn is starting qmail_local with the dash parameter set to a dash, and because of that it's not even checking whether or not Merc is a valid local user. Instead it's just looking for the .qmailXXX files, not finding them, and dying. Ben
HELP! qmail-local choking for only one user
Since yesterday evening, one of my users has not been receiving mail. Everyone else, including me, continues to receive/send mail with no problems. Here's a typical log sequence: 2000-06-20 08:54:18.530389500 starting delivery 50923: msg 124573 to local [EMAIL PROTECTED] 2000-06-20 08:54:18.530481500 status: local 10/10 remote 8/20 Then there are no more references to delivery 50923 in the log file, but what I see is a range of hanging processes, one for each message to "bob", as follows (ps -ef): bob 2725 2720 0 10:38:50 pts/1 0:00 bin/qmail-local -- bob /home/sebastian3/bob bob ifi.unizh.ch owner-sig-wtk We use dot-forward and procmail processing for local deliveries. I have checked the following - the user has no .qmail, .forward, or .procmail file - the user owns his directory, and it is not world writable - the user directory is mounted on the mail server - the user directory does not have the +t flag on it What else could it be that is causing qmail-local to hang, i.e. not defer or return some other status code. Any help much appreciated. FWIW, OS is Solaris 2.6 on an Enterprise 250 machine. regards, Will __ "I was going to be a Neo-Deconstructivist, but Mom wouldn't let me..." multimedia laboratorium [EMAIL PROTECTED] institut fuer informatik(pgp id)F703D035 der universitaet zuerich(office) +41 1 635 4346 winterthurerstr. 190(fax)+41 1 635 6809 ch-8057 zuerich (mobile) +41 76 372 0913 switzerland www.ifi.unizh.ch/~harris __
Re: qmail-local
Hi! I have now another solution, that is better, I think: There are two hosts, einstein and raman, serving the users home on both side of the WaveLAN. einstein is the main MX, raman the MX for the other side. ramanuser is a user behind the WaveLAN. On einstein the files ~alias/.qmail-ramanuser and ~alias/.qmail-ramanuser-default exist and contain "|/usr/bin/forward $[EMAIL PROTECTED]" The homedir of ramanuser is NFS-mounted on einstein from raman. The information is deployed via NIS. Under normal conditions einstein retrieves all mail and delivers them to the users homedir, for some user via NFS. Now if the NFS is not accessible because of an WaveLAN-outage, the ~alias/.qmail-ramanuser* files are used and the mail should be forwarded to raman via SMTP. And because raman is not reachable, the mail gets queued, generated by a temporary failure. Without that qmail-local would generate a permanent failure, resulting in a bounce message. The setup on raman is similar, it provides local mail delivery on the other side of the WaveLAN. Any comments? Greetings -- Robert Sander www.gurubert.de
qmail-local
Hi! I made this patch to qmail-local.c to enable only a temporary error if the NFS-mounted Homedir is not present: --- qmail-local.c.orig Tue May 23 09:11:37 2000 +++ qmail-local.c Tue May 23 09:11:43 2000 @@ -586,7 +586,7 @@ qmesearch(fd,flagforwardonly); if (fd == -1) if (*dash) - strerr_die1x(100,"Sorry, no mailbox here by that name. (#5.1.1)"); + strerr_die1x(111,"Sorry, no mailbox here by that name. (#5.1.1)"); if (!stralloc_copys(ueo,sender)) temp_nomem(); if (str_diff(sender,"")) Some of my users homedirs are mounted over an unreliable network (aka WaveLAN) that could sometimes fail. I need the qmail-local to just fail temporarily and try the delivery later again. Are the any side-effects with this? And how long is the timeout for the temporary deferral? Greetings -- Robert Sander www.gurubert.de
Re: qmail-local
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23 May 00, at 9:52, Robert Sander wrote: [snip] --- qmail-local.c.origTue May 23 09:11:37 2000 +++ qmail-local.c Tue May 23 09:11:43 2000 @@ -586,7 +586,7 @@ qmesearch(fd,flagforwardonly); if (fd == -1) if (*dash) - strerr_die1x(100,"Sorry, no mailbox here by that name. (#5.1.1)"); + strerr_die1x(111,"Sorry, no mailbox here by that name. (#5.1.1)"); if (!stralloc_copys(ueo,sender)) temp_nomem(); if (str_diff(sender,"")) [snip] Are the any side-effects with this? A message to a non-existent mailbox will also be held in queue and bounced after a long time. Not too nice, if the sender just misspelled the address and learns that not before a week. And how long is the timeout for the temporary deferral? control/queuelifetime, default 604800 seconds (7 days) man qmail-control, man qmail-send -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOSotNFMwP8g7qbw/EQKj8QCdFWBdUNylU3D/z7HQi1HGXUKlS9EAnj7q 8n/sdEaZ4yrnEBOKOa22VW18 =AUKZ -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: qmail-local
On Tue, May 23, 2000 at 10:03:16AM +0200, Petr Novotny wrote: A message to a non-existent mailbox will also be held in queue and bounced after a long time. Not too nice, if the sender just misspelled the address and learns that not before a week. Yes, but that should be ok, especially when I decrease the queuelifetime. Greetings -- Robert Sander www.gurubert.de
Re: qmail-local
On Tue, May 23, 2000 at 09:52:35AM +0200, Robert Sander wrote: [snip patch] Some of my users homedirs are mounted over an unreliable network (aka WaveLAN) that could sometimes fail. I need the qmail-local to just fail temporarily and try the delivery later again. We use users/assign for just that. It works perfectly. Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
Re: qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox
On Fri, Mar 31, 2000 at 01:47:48PM -0500, Dave Sill wrote: em9652015 [EMAIL PROTECTED] wrote: I have problem, while I try ps ax show this, qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox How I can turn off this option? This isn't an option, it's a misconfiguration. Look at the script that runs qmail-start: it's botched. Actually I have seen the exact same problem, I don't recally exactly what I did, but I know that I did qmail from source and then got the SysV scripts from www.qmail.org. Unfortunately, I forgot what exactly happened. Greetz, Peter. -- Peter van Dijk - student/sysadmin/ircoper/madly in love/pretending coder | | 'C makes it easy to shoot yourself in the foot; | C++ makes it harder, but when you do it blows your whole leg off.' | Bjarne Stroustrup, Inventor of C++
Re: qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox
On Fri, Mar 31, 2000 at 01:47:48PM -0500, Dave Sill wrote: em9652015 [EMAIL PROTECTED] wrote: I have problem, while I try ps ax show this, qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox How I can turn off this option? This isn't an option, it's a misconfiguration. Look at the script that runs qmail-start: it's botched. Actually this is quite a valid setup. A thing that I _do_ think is wrong with the SysV scripts on www.qmail.org is that they use a file called 'rc' with options named 'home' and 'proc' and stuff, but in a different format from the ones with qmail. This is what caught me by surprise back then. Greetz, Peter. -- Peter van Dijk - student/sysadmin/ircoper/madly in love/pretending coder | | 'C makes it easy to shoot yourself in the foot; | C++ makes it harder, but when you do it blows your whole leg off.' | Bjarne Stroustrup, Inventor of C++
Re: qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox
em9652015 [EMAIL PROTECTED] wrote: I have problem, while I try ps ax show this, qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox How I can turn off this option? This isn't an option, it's a misconfiguration. Look at the script that runs qmail-start: it's botched. -Dave
qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox
Hi, I have problem, while I try ps ax show this, qmail-lspawn # Using qmail-local to deliver messages to ~/Mailbox by default.??./Maibox How I can turn off this option? Thanks, Alex
qmail local
Hi, This is my /var/qmail/rc file. One line is commented out because it doesn't start the qmail local files. The defaultdelivery file has "./Maildir/" in it. I'm using the startup script from http://web.infoave.net/~dsill/lwq.html#installation-issues. Could someone tell me how to start the qmail local files correctly when using svscan and the daemontools? Any help is appreciated. exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Maildir/ splogger qmail #qmail-start "`cat /var/qmail/control/defaultdelivery`" darci
RE: qmail local
it. I'm using the startup script from http://web.infoave.net/~dsill/lwq.html#installation-issues. Could someone tell me how to start the qmail local files correctly when using svscan and the daemontools? Any help is appreciated. If you're using Dave Sill's startup setup from LWQ, the only change you should make to this file is remove the 'splogger qmail' phrase. If you don't remove it, logging will go to syslog, and never fall through to the multilog line Dave has in /var/qmail/supervise/qmail-send/log/run. You may or may not want to modify the "./Mailbox" part to deliver somewhere else, but that's a seperate issue. -- gowen -- Greg Owen -- [EMAIL PROTECTED]
Re: Mbox format with qmail-local possible?
On Sat, Jan 22, 2000 at 05:37:29PM +0900, Kristina wrote: Is there a way I can get qmail-local to deliver to /var/spool/mail/username file?? I know you can get the mbox format by using /bin/mail but I want mbox format delivery with qmail-local! qmail-local runs with the permissions of the user it is delivering to, and in general, ordinary users of a system do not have permission to write into /var/spool/mail, unless their mbox format file already exists, and is writable by the user. Normally, it would be present, but some programs remove it; if you can guarantee that all your users' mbox files will exist in /var/spool/mail, you could try: qmail-start '/var/spool/mail/$USER' -- See complete headers for more info
Mbox format with qmail-local possible?
Is there a way I can get qmail-local to deliver to /var/spool/mail/username file?? I know you can get the mbox format by using /bin/mail but I want mbox format delivery with qmail-local! Thankyou, Kristina
Re: Does qmail-local run more than 1 simultaneous instance?
[EMAIL PROTECTED] wrote: How do I start Qmail. Also How do I know how it is running. See: http://Web.InfoAve.Net/~dsill/lwq.html Specifically: http://Web.InfoAve.Net/~dsill/lwq.html#start-qmail http://Web.InfoAve.Net/~dsill/lwq.html#troubleshooting -Dave
Re: Does qmail-local run more than 1 simultaneous instance?
[EMAIL PROTECTED] wrote: Anyone know if more the one instance of qmail-local can be run simultaneously? Yeah, lot's people know the answer to that. Oh, OK, I'll answer it: yes. Up to concurrencylocal copies of qmail-local can be run simultaneously. See: http://Web.InfoAve.Net/~dsill/lwq.html#concurrencylocal -Dave
Re: Does qmail-local run more than 1 simultaneous instance?
Dave Sill writes: [EMAIL PROTECTED] wrote: Anyone know if more the one instance of qmail-local can be run simultaneously? Yeah, lot's people know the answer to that. Ask a silly person, and you get a silly answer. :) -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | "Ask not what your country 521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Does qmail-local run more than 1 simultaneous instance?
Anyone know if more the one instance of qmail-local can be run simultaneously? Need to know this to have .qmail-* run a magic program to deliver mail to a sql table. Don't want to flood mysql with too many connections. thanks
Re: Does qmail-local run more than 1 simultaneous instance?
How do I start Qmail. Also How do I know how it is running.
Re: when does qmail-local add the Deliverd-To line?
On Wed, Dec 08, 1999 at 04:41:13PM +0100, Markus Wuebben wrote:
Problem is now that I am missing the Delivered-To line, qmail normally
adds.
You can add it yourself by prepending $ENV{'DTLINE'} to the safecat input.
--
Jos Backus _/ _/_/_/ "Reliability means never
_/ _/ _/ having to say you're sorry."
_/ _/_/_/ -- D. J. Bernstein
_/ _/ _/_/
[EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer;
Re: when does qmail-local add the Deliverd-To line?
[EMAIL PROTECTED] wrote: This is how the .qmail-file looks like. | /usr/local/bin/myScript.pl Problem is now that I am missing the Delivered-To line, qmail normally adds. Why? Because you're delivering to a pipe, not a mailbox. (See "man qmail-command"). Try doing: | preline -f /usr/local/bin/myScript.pl -Dave
strange quirk in qmail-local
I am getting a wierd message pertaining to the sticky bit on users home directory. I know that chmod -t %HOME clears that, but after doing that I get a defferal_can't_chdir_to_Maildir. I have put a Maildir in my skeleton directory, in /etc I call qmail with ./Maildir/ in the line I have put a .qmail file also in the skeleton directory with an entry ./Maildir/ about 1/3 of my users get this, so it's not an isolated thing. What could be causing this, and how can I clear it up once and for all. Thanks Barry Smoke [EMAIL PROTECTED]
Re: strange quirk in qmail-local
"Barry Smoke" [EMAIL PROTECTED] wrote: I am getting a wierd message pertaining to the sticky bit on users home directory. And that message is? -Dave
Re: qmail local-error test failed
"Ernyo" [EMAIL PROTECTED] wrote: I followed the instruction by install.xxx text. Everything's OK until local-error test. When I sent a mail to an nonexistent local user, I didn't have a bounce message in my maildir. I saw the syslog, there was an error message _Unable to chdir to Maildir_ instead of _No such address_. What's wrong. I hope someone can help me! Undeliverable messages are delivered to the "alias" user's mailbox. If your default delivery type is "./Maildir", you need to create a ~alias/Maildir owned by "alias" using the maildirmake command to receive the bounces. -Dave
qmail local-error test failed
Hi! I followed the instruction by install.xxx text. Everything's OK until local-error test. When I sent a mail to an nonexistent local user, I didn't have a bounce message in my maildir. I saw the syslog, there was an error message _Unable to chdir to Maildir_ instead of _No such address_. What's wrong. I hope someone can help me! Thanx: Ernyo
usage of qmail-local
I am trying to write a wrapper function to assign directories to a number of mailing lists (created by ezmlm), before, i was putting a line in assign file of qmail for each mailing list like this +joe-testing:joe:uid:gid:directory of the dot-qmail files:-:testing: which works well and it handles the bounce messages as well, what i am doing now is that i have putted a line in the assign file +:joe:uid:gid:/mailinglist:-:: where /mailinglist is the directory of the wrapper function and a .qmail-default file calling the wrapper function in this directory |/mailinglist/mailinglist.pl in this wrapper function, it will find out which directory the mailing list's dot-qmail files are and calling qmail-local again to deliver the messages. I have no problem to receive messages by this wrapper function, which it can still distribute mailing list messages to subscribers, but when there is a bounce message from a invalid email address, it seems the bounce messages have never reach the right .qmail files and it has nothing in the bounce directory, that means the wrapper function has failed to deliver the bounce messages to the mailing list. I think i have mis-used the qmail-local program, does anyone has any idea how can i use qmail-local to have the same results as i putted the +joe-testing:joe:uid:gid:directory of the dot-qmail files:-:testing: in assign file? Thanks Joe
qmail-local performance
Dear All, How to increase qmail-local performance? (/var/qmail/control/concurrencylocal seems doesn't work) Thanks _Ayip. -- I THINK MAN INVENTED THE CAR by instinct. -- Jack Handley, The New Mexican, 1988.
new environment variable for qmail-local!!
hi, some days ago i posted to this list asking for the possibility to add a environment variable to qmail-local. here again my question: anybody got an idea how to add an environment variable MESSAGESIZE to qmail-local? this would be great for message routing depending on their size. i tried this with several `wc -c` commands but it's is not a good approach. working with env var. would be much more better! i am a poor programmer so i do not have any idea how to add this feature to qmail-local. i had a look into the sources and i found the place where all the other env. var. are set. i think it must be easy for a skilled programmer to add a system-call getting the message size from the file in the mess directory! regards jodok
Re: qmail-local
Marcel Dan [EMAIL PROTECTED] wrote: I am unsure of how to change the default route of qmail for the entire server. I am using qmail with vchkpw so the domain is not virtual but the users are and the message gets delivered by defualt into a users /home/directory (which doesn't exist). Everything else is working so that I can upload messages and relay...etc. I sincerely apprectiate any information/help. I'm not familiar with vchkpw, but it's not clear exactly what you're trying to accomplish. Does delivery to real users work? Have you created maildirs for the virtual users? -Dave
Re: qmail-local
Dave Sill wrote: I'm not familiar with vchkpw, but it's not clear exactly what you're trying to accomplish. Does delivery to real users work? Have you created maildirs for the virtual users? -Dave Delivery to real users does work and the virtual users are created with a Maildir format. When q-mail excepts a message it delivers it to /home/user/ so I think that the problem might be in that I have to make q-mail not know the host name so that it will send the message through the control/virtualdomains file and users/assign (used by the virtual user/domain program - http://www.nccnet.co.uk/~sixie/qmail/vchkpw.html) file so that I can control the delivery. Thanks for the response. Marcel
qmail-local
Hi, I am unsure of how to change the default route of qmail for the entire server. I am using qmail with vchkpw so the domain is not virtual but the users are and the message gets delivered by defualt into a users /home/directory (which doesn't exist). Everything else is working so that I can upload messages and relay...etc. I sincerely apprectiate any information/help. Marcel
strange problems with qmail-local
I can't understand, where is the problem.
System is OpenBSD-current. Qmail version is 1.3.
Any command in .qmail* files doesn't execute.
What i learn from code (I'm not C programmer - don't laugh please :)
This is that part of code where execution of program from .qmail* happens:
switch(child = fork())
{
case -1:
temp_fork();
case 0:
args[0] = "/bin/sh"; args[1] = "-c"; args[2] = prog; args[3] = 0;
sig_pipedefault();
execv(*args, args);
strerr_die3x(111,"Unable to run /bin/sh: ",error_str(errno),". (#4.3.0)");
}
Looks like forking and execv() happens (if I 'mv /bin/sh /bin/sh~' qmail-local
writes error message to syslog). /bin/sh works.
My .qmail file:
-- .qmail ---
./Maildir/
|/var/qmail/bin/qbiff
--- end of .qmail ---
Output of '/var/qmail/bin/qmail-local -n pvk /home/users/pvk/ '' '' '' \
mail.tsinet.ru [EMAIL PROTECTED] postmaster':
maildir ./Maildir/
program /var/qmail/bin/qbiff
did 1+0+1
If i put something like this to ~/.qmail:
|lkjsdlkfjsdlkfhsdlkfhsldkfhsdlkfhsdlkfhsldkfhsdlkfh
it writes error to syslog:
May 10 08:39:56 gw-nat1 qmail: 926311196.381569 delivery 4: deferral:
/bin/sh:_lkjsdlkfjsdlkfhsdlkfhsldkfhsdlkfhsdlkfhsldkfhsdlkfh:_not_found/
So where is the problem? All qmail programs work correctly, but qmail-local.
Any suggestions?
---
Pavel Korovin
SMTP: [EMAIL PROTECTED]
PSTN: +7 (095) 721-26-00
Problem with qmail-local
Hello, I am sorry if this problem was discussed before, but I could'nt find it. And I do not know anybody who can fix it. So to the point: I have qmail-1.03 I use /var/spool/mail with mbox format of mailboxes. I use '|preline procmail' directive to filter mail. And i would like qmail-local to deliver mail to /var/spool/mail ... I don't know how to do it. Second Question: Can I remove qmail-local and use procmail instead of qmail-local. ? (to deliver mail to /var/spool/mail) Thanks for help .. . -- Lukas Futera [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
qmail-local error
hi, I get this error in /var/log/qmail : ... delivery 1 : deferral : Unable_to_chdir_to_maildir._ (#4.2.1)/ I have in passwd file, home directory : /var/log/qmail/maildirs/digicom-bg/xxx Also in users/assign (it is compiled in cdb) =xxx:xxx:82:80:/var/qmail/maildirs/digicom-bg/xxx::: .. In ./defaultdelivery/rc /var/qmail/maildirs/ Also I tried : qmail-local -n xxx '/var/qmail/maildirs/digicom-bg/xxx' xxx '' '' '' '' '/var/qmail/maildirs/digicom-bg/' and I get the following result : maildir /var/qmail/maildirs/digicom-bg/xxx/ did 1+0+0 Where I'm wrong. Please help me = [EMAIL PROTECTED] =
Alias, dot-qmail, qmail-local, maildir, directories
Couple of questions: 1. I cannot get "redirection" to work when I use a .qmail file containing a complete maildir path. If I replace the maildir path with another local user, the redirection works. In the former case, qmail(-local I assume) complains about delivery being temporarily deferred. What I had was: .qmail-john:doe In the default home directory. The file contained /home/special/mailadd/johndoe02/Maildir/ The ./johndoe02 directory is owned by johndoe02 (not world writeable) The same ownership applies to all of the directories below ./johndoe02 If I log-in as johndoe02, I can change to /home/special/mailadd.. although I cannot do a pwd. What does qmail(-local) require as far as directory rights in the above scenario. I have temporarily circumvented the problem by replacing the path specification in the .qmail-john:doe file with 'johndoe02', which works but isn't an elegant solution (IMHO) since it requires extra work on qmail's behalf. 2. Is there a file or document which describes which directories must be owned/groupowned by the various qmail UIDs/GIDs as well as other directories (such as the one in the first question above)? I'm somewhat behind in this mailing list, so if you do reply, please CC me ([EMAIL PROTECTED]) on your reply. Thanks. -+- Joaquim Homrighausen * [EMAIL PROTECTED] * 2:201/330@fidonet Definite Solutions * Stockholm, Sweden Phone: +46 8 6505087 * Fax: +46 8 4410010 * http://www.defsol.se -+-
huge problem using qmail-local/lspawn
Dear Fellows, Hello! Our server had been running qmail-1.02 for quite sometime. Recently, there were few problems encountered. I have no idea whether sysad had any hand in it or not. Problem 1. The remote mails were delievered instantly but the local mails were not at all delivered. as a result we could not get any mails. The logs showed upto 1400 local message nos. and the status line read status: local 10/10 remote 0/20(or 5/20) till the sysad forced qmail to deliever the local messages. There were once so many mails and the logs were really mounting up so mush so that /var became full. the sysad then removed the log files manually. Problem 2. After a reboot the problem really grew. qmail just couldnt restart. the system logs was full of similar mesg. alert: unable to open(/read) todo/some no.s or alert: unable to open(/read) mess/some.nos or alert: unable to opendir todo, sleeping... All this time the logfile was increasing by Mb' severy minute and within few minutes the /var was full again. and since then its not been working at all. A similar installation of qmail exists on another server which we are using at present. Any insight into the above problems would be helpful. Thanks and regards, -- Sameer Vijay - [EMAIL PROTECTED] (Research Engineer) Dept. of Chemical Engg, IIT Bombay, Mumbai 400076 INDIA. Fax: +91-22-5796895 (dept), +91-22-5783480 (IITB)
Re: huge problem using qmail-local/lspawn
At 06:24 PM 3/7/99 +0530, Sameer Vijay wrote: Dear Fellows, Hello! Our server had been running qmail-1.02 for quite sometime. Recently, there were few problems encountered. I have no idea whether sysad had any hand in it or not. Problem 1. The remote mails were delievered instantly but the local mails were not at all delivered. as a result we could not get any mails. The logs showed upto 1400 local message nos. and the status line read status: local 10/10 remote 0/20(or 5/20) till the sysad forced qmail to deliever the local messages. Why not show is some log messages associated with the local delivery attempts. We cannot guess what those entries are. There were once so many mails and the logs were really mounting up so mush so that /var became full. the sysad then removed the log files manually. Problem 2. After a reboot the problem really grew. qmail just couldnt restart. the system logs was full of similar mesg. alert: unable to open(/read) todo/some no.s or alert: unable to open(/read) mess/some.nos or alert: unable to opendir todo, sleeping... Please don't sanitize log entries if you want a response. As has been said many times on this list - sanitized log messsages often hide the true nature of the problem. If confidentiality is an issue such that you cannot disclose the log files to the list, you may want to contract one of the commercial support people listed on www.qmail.org Regards.
