scan-4-virus NAI not stopping SirCam
Anybody else got this issue? I'm using .95 and latest DAT (7/22) Thanks all. John McCoy, Jr Central Systems Administrator Mills College, Oakland, CA 510-430-3321 [EMAIL PROTECTED]
qmail-inject and Qmail-scanner on local message
Our web mail (IMP 2.2.4) program injects all mail using qmail-inject, when the email is totally local (i.e. never travels through SMTP) it is never scanned. I've tried adding the QMAILQUEUE variable into Apache to try to trigger the scan but I think it is to far down the loop. Any one have any ideas on this, I am using the qmailqueue.patch maybe if I replaced qmail-queue instead? Thanks for anything. John McCoy, Jr Central Systems Administrator Mills College, Oakland, CA 510-430-3321 [EMAIL PROTECTED]
RE: qmail-inject and Qmail-scanner on local message
I can see it set in phpinfo() output, but do not know if this is a good test for that. Thanks. -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 12:18 PM To: qmail@list. cr. yp. to Subject: Re: qmail-inject and Qmail-scanner on local message John McCoy, Jr. [EMAIL PROTECTED] wrote: Our web mail (IMP 2.2.4) program injects all mail using qmail-inject, when the email is totally local (i.e. never travels through SMTP) it is never scanned. I've tried adding the QMAILQUEUE variable into Apache to try to trigger the scan but I think it is to far down the loop. No -- qmail-inject calls qmail-queue and therefore should be affected by Bruce's QMAILQUEUE patch. Are you sure your web mail program isn't running qmail-inject in a scrubbed environment? Or that Apache isn't doing that? 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. ---
scan4virus without qmail-smtpd
Is it possible to get scan4virus to scan email that does not pass through qmail-smtpd? I am trying to get email sent through IMP (www.horde.org) Webmail to be scanned. I have tried setting the Environment Variable in Apache but that didn't work. I am now trying to get it to work through simple shell scripts and am not having any luck there either. Here is what I am trying to do: #!/bin/sh QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue.pl; export QMAILQUEUE /var/qmail/bin/qmail-inject [EMAIL PROTECTED] EOF To: [EMAIL PROTECTED] virus (SNIPED) I know the scanner will find the virus I am sending when sent through Outlook/Netscape. Should this be possible? Is qmail-inject erasing QMAILQUEUE? Any ideas? Thanks all. John McCoy, Jr Central Systems Administrator Mills College, Oakland, CA 510-430-3321 [EMAIL PROTECTED]
qmail-remote with tls crash again
I have two boxes both with qmail 1.03 qmailqueue.patch.txt (for qmail-scanner.0.95) and the latest tls.patch. I was never able to get qmail-remote working on the primary box as it would crash when sending to yahoo.com. On the secondary box I have it working, except now it can't deliver to the primary box, but yahoo is fine. I want to use the secondary box as my mail gateway/virus scanner. I have tried running qmail-remote under truss (which I don't really understand), by replacing qmail-remote with: #! /bin/sh truss -o /tmp/qr.truss.$$ /var/qmail/bin/qmail-remote-original $* But this fails to run qmail-remote at all (I do get a bounce from qmail).If I don't add the tls patch it delivers just fine to the primary. I have increased the timeout in qmail-remote.c from 60 to 120, but that didn't help. I am using a self signed cert on the secondary box and a real commercial cert on the primary. Is this likely the Primary still messing up? Thanks all. All systems are: Solaris 7 gcc 2.95.3 openssl .0.9.6 John McCoy [EMAIL PROTECTED] Systems Administrator Central Systems Mills College 510-430-3321
qmail-remote crash truss output, help please
OK I finally got qmail-remote to run under truss from the command line. Here
is what I see:
open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT
What? Why? I can't find this file on any system I have (Solaris and Linux)
open64("/var/qmail/bin/qmail-remote", O_RDONLY) = 3
close(19) Err#9 EBADF
I've gotten the same results with qmail-remote ownded by root:other and
qmailr:qmail.
Here are the remaining errors that I didn't get at all:
fcntl(19, F_SETFD, 0x0001) = 0
ioctl(2, TCGETA, 0xFFBEF9AC)= 0
ioctl(19, TCGETA, 0xFFBEF9AC) Err#25 ENOTTY
read(19, " # ! / b i n / s h\n / u".., 128) = 85
brk(0x00039918) = 0
fork() = 9675
waitid(P_PID, 9675, 0xFFBEF8A8, WEXITED|WTRAPPED|WNOWAIT) = 0
ioctl(0, TIOCGPGRP, 0xFFBEF864) = 0
ioctl(0, TCGETS, 0x0003836C)= 0
waitid(P_PID, 9675, 0xFFBEF8A8, WEXITED|WTRAPPED) = 0
brk(0x00039718) = 0
read(19, 0x00038478, 128) = 0
ioctl(19, TCGETA, 0xFFBEF944) Err#25 ENOTTY
ioctl(19, TCGETA, 0xFFBEF9A4) Err#25 ENOTTY
close(19) = 0
llseek(0, 0, SEEK_CUR) = 165841
_exit(0)
I don't see a big blow out but I really have no clue.
Thanks for any help you can give.
John McCoy [EMAIL PROTECTED]
Systems Administrator
Central Systems
Mills College
510-430-3321
qmail Virus Scanner Memory question
I'm using qmail-scanner-0.95 to implement virus scanning, I've got the patches all applied and things compile just fine. However when I put the pieces in place I get this error: libthread panic: _sys_thread_create():alloc_thread returns 0 (no mem) : dumping core (PID: 26646 LWP 1) I reading this, as there is not enough memory to run the scanner, is this correct? I am set up using the Life with qmail method so here is my qmail/supervise/qmail-smtpd/run file: #!/bin/sh QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" export QMAILQUEUE QMAILDUID=`/usr/xpg4/bin/id -u qmaild` NOFILESGID=`/usr/xpg4/bin/id -g qmaild` exec /usr/local/bin/softlimit -m 600 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp \ /var/qmail/bin/qmail-smtpd 21 I've read in the archives that most people had success with setting the softlimit to 600, I guess I'm just a little wary about going much higher, also I'm unsure if the number of incoming connections is limited, I would need it to be no more then 50. System Spec: Sol 7 Sparq Qmail-1.03 with tls qmail-queue patches NAI 4.x scanner gcc Thanks all. **** John McCoy, Jr Central Systems Administrator Mills College, Oakland, CA 510-430-3321 [EMAIL PROTECTED]
RE: qmail Virus Scanner Memory question
Will do, still questioning where the limit on concurrent incoming smtp connections is set? I'm sure it's in the Doc's but 20 things to do you know. John McCoy, Jr Central Systems Administrator Mills College, Oakland, CA 510-430-3321 [EMAIL PROTECTED] -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 27, 2001 8:53 AM To: qmail@list. cr. yp. to Subject: Re: qmail Virus Scanner Memory question John McCoy, Jr. [EMAIL PROTECTED] wrote: I'm using qmail-scanner-0.95 to implement virus scanning, I've got the patches all applied and things compile just fine. However when I put the pieces in place I get this error: libthread panic: _sys_thread_create():alloc_thread returns 0 (no mem) : dumping core (PID: 26646 LWP 1) I reading this, as there is not enough memory to run the scanner, is this correct? Yes. I am set up using the Life with qmail method so here is my qmail/supervise/qmail-smtpd/run file: #!/bin/sh QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" export QMAILQUEUE QMAILDUID=`/usr/xpg4/bin/id -u qmaild` NOFILESGID=`/usr/xpg4/bin/id -g qmaild` exec /usr/local/bin/softlimit -m 600 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp \ /var/qmail/bin/qmail-smtpd 21 I've read in the archives that most people had success with setting the softlimit to 600, I guess I'm just a little wary about going much higher, also I'm unsure if the number of incoming connections is limited, I would need it to be no more then 50. System Spec: Sol 7 Sparq Solaris binaries are bloated; it probably will require more than the 6MB others have found success with. Try raising it to 8MB, or 10MB, and see if it fixes the 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: Bare linefeeds not accepted by Qmail?
Could this be applied to a single user on a machine. Our web reporting software sends the wrong linefeeds, but we have cgi scripts that work correctly? John McCoy [EMAIL PROTECTED] Systems Administrator Central Systems Mills College 510-430-3321 - Original Message - From: "Charles Cazabon" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 08, 2001 7:55 AM Subject: Re: Bare linefeeds not accepted by Qmail? Cameron Childress [EMAIL PROTECTED] wrote: I'm still in discussions/arguments with the software company, who apparently uses Netscape's Messaging library to support their SMTP operations, to change their product so that it does not generate bare LFs. I'm not sure what progress I'm going to make with that, but any advice would be appreciated. On the other hand, I am going to take a stab at convincing my ISP to change their Qmail implementation so that it will accept bare LFs and convert them into CRLFs. I have found reference to a solution in the list archives (link below), but unfortunately, being completely unfamiliar with Qmail's internals, I am not going to be able to clearly communicate the solution to the engineers at my ISP based on this posting. Something like fixcrio may do the trick for them; however, it's not good practice to mangle customers' mail for them, as you can corrupt otherwise properly formatted messages. You have other options open which do not involve having the ISP change anything. You could set up a simple qmail relay on your internal network; have it pipe everything through fixcrio (with Dan's @fixme/fixup trick and tcpserver), and use smtproutes to send all mail from there to your ISP's smarthost. Then have your special (broken) software send its mail to that machine instead of directly to your ISP's smarthost. You could probably even do something simpler: use tcpserver, fixcrio, tcpclient, and some shell magic to run this mail through fixcrio on the fly, communicating directly with your ISP's smarthost from the broken application. I haven't looked at this enough to know quite how to set it up. What I am searching for is something similar to a Knowledge Base or FAQ article which would either assist me in understanding the changes which should be made, or that I could simply point the engineers at my ISP to. Without that, I am not sure that I will be able to effectively communicate the problem/solution. This link might help: http://cr.yp.to/docs/smtplf.html But it helps your ISP's case, not yours. It basically says "qmail does it right, fix your broken client. Here's some broken clients, and how to fix them...". 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. ---
rblsmtpd logging
I noticed when I implemented rblsmtpd that several legitimate sites were being blocked. They were mostly other .edu sites. Is there any way to create a list of exceptions, hopefully with a wild card so I could allow all .edu traffic to pass regardless? Or better yet can I get rblsmtpd to just tell me which sites it has gotten matches on but not actually block the mail. So I can then encourage sites that should be allowed in to improve their servers, and make the web a better place for us all. I've already written a script to pull out those who get blocked from the log file. That was how I discovered I was blocking people who needed to send us email. I would be happy to share it. John McCoy, Jr Central Systems Administrator Mills College, Oakland, CA 510-430-3321 [EMAIL PROTECTED]
tls.patch causing qmail-remote to crash
Mostly this occurs when delivery to yahoo is attempted, I have seen only one other site crash it. I have tried both Messenger 4.76 and Outlook Express they both are able to use the secure SMTP connection. Many other severs are able to connect just fine. Any body got any ideas? I have not tried to set up advanced relaying or anything, just want basic encrypted communication for now. I am even willing to only patch qmail-smtpd.c + Makefile, but I have no idea how to do this. Please help!!! Solaris 7 (Sparq) Qmail 1.03 gcc 2.95.2 GNU patch (Solaris one fails a lot) tls.patch 20010106 John McCoy [EMAIL PROTECTED] Systems Administrator Central Systems Mills College 510-430-3321
Cert format for tls SMTP patch
I've been having some trouble with this. I have it working fine with UW-IMAP-2000c. I copied just the cert to /var/qmail/control/cert.pem it complained about no key. I then copied the imapd.pem (cert and key -no password) to cert.pem same problem, I tried creating a separate prvtkey.pem file still no good, what am I missing? Thanks all Solaris 7 (Sparq) qmail 1.03 UW-Imap-2000c John McCoy [EMAIL PROTECTED] Systems Administrator Central Systems Mills College 510-430-3321
Certificate format for tls.patch PLEASE
Exactly what certs and keys are needed and in what format? Thanks John McCoy [EMAIL PROTECTED] Systems Administrator Central Systems Mills College 510-430-3321
Re: Certificate format for tls.patch PLEASE
No one responded to me when I spelled it out. here is the Makefile stuff: cert: /usr/local/ssl/bin/openssl req -new -x509 -nodes \ -out /var/qmail/control/cert.pem -days 366 \ -keyout /var/qmail/control/cert.pem chmod 640 /var/qmail/control/cert.pem chown qmaild.qmail /var/qmail/control/cert.pem cert-req: /usr/local/ssl/bin/openssl req -new -nodes \ -out req.pem \ -keyout /var/qmail/control/cert.pem chmod 640 /var/qmail/control/cert.pem chown qmaild.qmail /var/qmail/control/cert.pem @echo @echo "Send req.pem to your CA to obtain signed_req.pem, and do:" @echo "cat signed_req.pem /var/qmail/control/cert.pem" This looks to me like the commands for requesting a cert and key. I already have them. I need to know how qmail is going to want them now, some programs want them in a single file with no password protection, I tried that it didn't work. Others want to seperate files and will prompt you for a password as they start up, that didn't work either. That is all I know how to do, is there another way? I tried two files without a password on the privet key too. Do I need a CA file possibly? - Original Message - From: "Jamie Heilman" [EMAIL PROTECTED] To: "John McCoy, Jr" [EMAIL PROTECTED] Cc: "Qmail" [EMAIL PROTECTED] Sent: Tuesday, February 27, 2001 1:11 PM Subject: Re: Certificate format for tls.patch PLEASE John McCoy, Jr wrote: Exactly what certs and keys are needed and in what format? Did you read the patch? Do you understand how SSL certificates work? - provide a certificate in /var/qmail/control/cert.pem. "make cert" makes a self-signed certificate. "make cert-req" makes a certificate request. Note: nsCertType must be = server,client or be a generic certificate (no usage specified). If you want to use a separate cert in qmail-remote (SMTP client), then s/cert\.pem/clientcert\.pem/ in qmail-remote.c. cert.pem must be a complete certificate, private key and all. Read the Makefile post-tls-patch and see what the 'cert' target and the 'cert-req' target do, it should answer both your questions. -- Jamie Heilman http://audible.transient.net/~jamie/ "I was in love once -- a Sinclair ZX-81. People said, "No, Holly, she's not for you." She was cheap, she was stupid and she wouldn't load -- well, not for me, anyway." -Holly
Re: Certificate format for tls.patch PLEASE
That got it but is causing a more serous problem: starting delivery 1017: msg 229980 to remote mailto:[EMAIL PROTECTED] 2001-02-27 16:58:55.995301500 delivery 1017: deferral: qmail-remote_crashed./ Every delivery to yahoo causes a crash of qmail remote!!! Any idea? Thanks for the help, I was forgetting the chmod. - Original Message - From: "Jamie Heilman" [EMAIL PROTECTED] To: "John McCoy, Jr" [EMAIL PROTECTED] Cc: "Qmail" [EMAIL PROTECTED] Sent: Tuesday, February 27, 2001 3:46 PM Subject: Re: Certificate format for tls.patch PLEASE John McCoy, Jr wrote: No one responded to me when I spelled it out. That happens, life's a bitch. here is the Makefile stuff: [snip] This looks to me like the commands for requesting a cert and key. I already have them. I need to know how qmail is going to want them now, some programs want them in a single file with no password protection, I tried that it didn't work. Have you tried running them and examining the output? Then maybe comparing them to the cert data you have? I already said that both the key and the cert need to be in the file. Which if you examine those make commands is exactly what you end up with. How did you test your setup with the key+cert combo? What is "didn't work"? Others want to seperate files and will prompt you for a password as they start up, that didn't work either. That is all I know how to do, is there another way? I tried two files without a password on the privet key too. Do I need a CA file possibly? Everything you need to know is in the header of the patch file. It tells you every additional control file, and what they are used for. It gives examples of how to generate them. You may need a list of CAs, it depends on which aspect of SMTP/TLS you are trying to make work. If you want to allow relaying based on signed personal certificates, for example, you will need a list of CAs which you want to accept placed into /var/qmail/control/clientca.pem as well as the email addresses placed in /var/qmail/control/tlsclients -- Jamie Heilman http://audible.transient.net/~jamie/ "We must be born with an intuition of mortality. Before we know the words for it, before we know there are words, out we come bloodied and squalling with the knowledge that for all the compasses in the world, there's only one direction, and time is its only measure." -Rosencrantz
listproc to ezmlm, anyone done this???
Is there an easy way to convert the archives? * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] *
qmail ignoring default delivery
I used the life with qmail instructions and set up to deliver to ~/INBOX. This was working fine, and then all of a sudden it stopped. Mail is now being delivered to /var/mail/username. This behavior seemed to have started when a crontab auto-email was sent to root then redirected via alias to me. Seems very strange. * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] *
My BAD!!! RE: qmail ignoring default delivery
I forgot I had restored accounts from the server about to be replaced, all the user accounts had .qmail files telling it to put mail in /var/mail/ Thanks for the quick response though. * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] * -Original Message- From: John McCoy, Jr [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 15, 2000 10:52 AM To: [EMAIL PROTECTED] Subject: qmail ignoring default delivery I used the life with qmail instructions and set up to deliver to ~/INBOX. This was working fine, and then all of a sudden it stopped. Mail is now being delivered to /var/mail/username. This behavior seemed to have started when a crontab auto-email was sent to root then redirected via alias to me. Seems very strange. * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] *
How to stop sub-domains in BADMAIL
Sorry this has probably been asked a thousand times but here it is. We keep getting spam from zzn.com, but with sub domains, so it's yes.zzn.com or friend.zzn.com I know to stop them by putting this in BADMAIL @friend.zzn.com @yes.zzn.com Can I do it this way? @*.zzn.com Thanks all * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] *
Thanks, eric RE: queue-fix 1.4 won't compile on IRIX6.5.3m
I was afraid of that, looks like I need to do an emergency queue rebuild instead, without re-importing the old queue. * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] * -Original Message- From: Eric Huss [mailto:[EMAIL PROTECTED]] Sent: Monday, April 24, 2000 8:28 PM To: John McCoy, Jr Cc: [EMAIL PROTECTED] Subject: Re: queue-fix 1.4 won't compile on IRIX6.5.3m Sounds like a bug in the Irix linker. Try looking to your OS vendor for patches. Or you can try installing gnu binutils (and then recompiling gcc instructing it to use the binutils version of ld). However, this is a tricky and dangerous path to take. -Eric Unfortunately I'm still new to all this, I have made sure I have the latest versions of gcc++ and it's libraries. I've been able to compile the program on Solaris 2.6 7 boxes without a problem, however the broken queue is on the SGI box. Has any body tried this under IRIX? Eric you mentioned libraries from D.J. Bernstein, do I need to get these? Can I use qmail-sanity's output and go in and delete files manually, instead? Help I'm desperate, my maillog file grows by 1Meg every couple hours!!!
queue-fix 1.4 won't compile on IRIX6.5.3m
I've been trying to figure this one out with no luck. When compiling queue-fix it gives the following error: ./makelib str.a str_len.o str_diff.o str_diffn.o str_cpy.o \ str_chr.o str_rchr.o str_start.o byte_chr.o byte_rchr.o \ byte_diff.o byte_copy.o byte_cr.o byte_zero.o ./load queue-fix fifo.o fs.a stralloc.a getln.a open.a error.a \ substdio.a alloc.a str.a ld32: Segmentation fault. Removing output file... *** Error code 1 (bu21) Unfortunately I'm still new to all this, I have made sure I have the latest versions of gcc++ and it's libraries. I've been able to compile the program on Solaris 2.6 7 boxes without a problem, however the broken queue is on the SGI box. Has any body tried this under IRIX? Eric you mentioned libraries from D.J. Bernstein, do I need to get these? Can I use qmail-sanity's output and go in and delete files manually, instead? Help I'm desperate, my maillog file grows by 1Meg every couple hours!!! Thanks Box info: SGI Indy r5000 IRIX 6.5.3m Gcc 2.8.1 256Megs RAM Lots of disk space. Qmail 1.03 (fairly normal, no pop3 or extras) Typical maillog entries: Apr 24 19:52:19 4C:ella qmail: 956605939.916525 warning: unable to stat mess/1/53499 Apr 24 19:52:19 4C:ella qmail: 956605939.916756 warning: unable to stat mess/11/53486 Apr 24 19:52:19 4C:ella qmail: 956605939.917012 warning: unable to stat mess/11/30900 Apr 24 19:52:19 4C:ella qmail: 956605939.917247 warning: unable to stat mess/11/52819 Apr 24 19:52:19 4C:ella qmail: 956605939.917478 warning: unable to stat mess/11/53003 Apr 24 19:52:20 6C:ella qmail: 956605940.106213 delivery 123293: success: did_1+0+0/ Apr 24 19:52:20 6C:ella qmail: 956605940.126366 status: local 0/25 remote 1/20 Apr 24 19:52:20 4C:ella qmail: 956605940.356701 warning: trouble injecting bounce message, will try later Apr 24 19:52:20 4C:ella qmail: 956605940.586380 warning: trouble injecting bounce message, will try later Apr 24 19:52:20 6C:ella qmail: 956605940.587046 end msg 4134 * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] *
RE: Messages stuck in queue
I got queue-fix but it wont compile I get this at the very end of the compile: ld32: Segmentation fault. Removing output file... *** Error code 1 (bu21) System: SGI Indy r5000 IRIX 6.5.3m let me know if you need more I'm not sure of the version of gcc installed. Sorry I'm still a newbie but I'm confused by this error, I'm guessing it was unable to do a link. I compiled on a SUN box without a problem. Thanks * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] * -Original Message- From: Steve Wolfe [mailto:[EMAIL PROTECTED]] Sent: Friday, April 14, 2000 8:54 AM To: [EMAIL PROTECTED] Subject: Re: Messages stuck in queue I've got a bunch of messages that the systems seems unable to process, can they be removed without the seemingly painful process of removing the queue? Here is the log: Apr 14 15:45:47 4C:ella qmail: 955727147.699527 warning: unable to stat mess/11/52359 Apr 14 15:45:47 4C:ella qmail: 955727147.722880 warning: unable to stat mess/11/53440 It looks like someone renamed or moved the queue. Download queue-fix from www.qmail.org, run it, and you should see those messages get delivered succesfully. steve
Messages stuck in queue
I've got a bunch of messages that the systems seems unable to process, can they be removed without the seemingly painful process of removing the queue? Here is the log: Apr 14 15:45:47 4C:ella qmail: 955727147.699527 warning: unable to stat mess/11/52359 Apr 14 15:45:47 4C:ella qmail: 955727147.722880 warning: unable to stat mess/11/53440 Apr 14 15:45:47 4C:ella qmail: 955727147.725018 warning: unable to stat mess/11/53463 Apr 14 15:45:47 4C:ella qmail: 955727147.725336 warning: unable to stat mess/11/19975 Apr 14 15:45:47 4C:ella qmail: 955727147.725568 warning: unable to stat mess/1/53476 Apr 14 15:45:47 4C:ella qmail: 955727147.725798 warning: unable to stat mess/5/53480 Apr 14 15:45:47 4C:ella qmail: 955727147.726026 warning: unable to stat mess/1/53499 These keep going round and round, I have about 350 messages always in the queue, is this normal for a site with 1,300 accounts? * John McCoy, Jr Systems Administrator Central Systems, Mills College 510-430-3321 [EMAIL PROTECTED] *
