qmail Digest 14 Sep 2000 10:00:01 -0000 Issue 1123
Topics (messages 48549 through 48695):
Re: linuxpeople thread
48549 by: linuxpeople.hotmail.com
48550 by: Russ Allbery
48551 by: linuxpeople.hotmail.com
48555 by: Steve Carter
48556 by: linuxpeople.hotmail.com
48559 by: Peter Green
48560 by: linuxpeople.hotmail.com
48564 by: linuxpeople.hotmail.com
48568 by: Chris Johnson
48571 by: linuxpeople.hotmail.com
48572 by: linuxpeople.hotmail.com
48574 by: Tim Hunter
48575 by: Oliver Koch
48577 by: Oezguer Kesim
48578 by: Jason Brooke
48579 by: Robin S. Socha
48582 by: Justin Bell
48586 by: Stephen Bosch
48587 by: Frank Tegtmeyer
48590 by: David Gadoury
48591 by: David Gadoury
48600 by: Michael T. Babcock
48601 by: Felix von Leitner
48614 by: David Dyer-Bennet
48615 by: David Dyer-Bennet
48616 by: David Dyer-Bennet
48627 by: Peter Green
48639 by: Nathan J. Mehl
48641 by: Nathan J. Mehl
48661 by: Russ Allbery
48671 by: Vincent Schonau
Re: Good review of qmail on securityfocus.com
48552 by: Dave Burke
TCP server
48553 by: Jonathan Fanti
48588 by: David Gadoury
REPOST: mail works, kmail/NS messenger doesn't on private WAN
48554 by: Phil Rhoades
48557 by: Vince Vielhaber
48567 by: Phil Rhoades
48573 by: Vince Vielhaber
Re: REPOST: mail works, kmail/NS messenger doesn't on private WA
48558 by: Frank Tegtmeyer
Re: duplicate messages RESOLVED
48561 by: James T. Perry
change virtual host bounce address
48562 by: Magnus �
48563 by: Petr Novotny
48589 by: Johan Almqvist
Re: Questions...
48565 by: Jost Krieger
48603 by: Michael T. Babcock
Re: domain..
48566 by: Melanie Desaive
48570 by: Ricardo Cerqueira
Re: qmail pop
48569 by: Chris Johnson
48595 by: Dave Sill
qmail-cyrus
48576 by: Galen Johnson
Re: Linuxluser thread (Was: linuxpeople thread)
48580 by: Stephen Bosch
48583 by: linuxpeople.hotmail.com
48585 by: Robin S. Socha
48604 by: Michael T. Babcock
48607 by: markd.bushwire.net
48613 by: Michael T. Babcock
48684 by: Eric Cox
Re: Looking for input on JFS for linux.
48581 by: Jeff Hayward
Re: REPOST: mail works, kmail/NS messenger doesn't on private W
48584 by: Frank Tegtmeyer
qmail on little machines? (was part of linuxuser thread)
48592 by: Ihnen, David
48597 by: markd.bushwire.net
48617 by: David Dyer-Bennet
48619 by: Stephen Bosch
48625 by: Ihnen, David
48629 by: Steven Rice
48631 by: Oezguer Kesim
48632 by: Steve Wolfe
48635 by: Stephen Bosch
qmail-pop3d not picking up new messages?
48593 by: Toni Mueller
48598 by: markd.bushwire.net
Re: rblsmtpd emergency
48594 by: Toni Mueller
Re: Which to choose?
48596 by: Dave Sill
Re: Mass Mailout Performance Tips
48599 by: Michael T. Babcock
48610 by: David Dyer-Bennet
48664 by: John R. Levine
Blocking certain mail with no "From"
48602 by: Hubbard, David
48687 by: Erwin Hoffmann
48693 by: Eric Cox
C API for queueing messages
48605 by: Jay Balakrishna
48609 by: markd.bushwire.net
48621 by: Jay Balakrishna
48626 by: markd.bushwire.net
48662 by: Russ Allbery
48681 by: Russell Nelson
hosts not known by DNS
48606 by: A.Woerner.eMessage.de
48608 by: Chris Johnson
48611 by: Dave Sill
48612 by: markd.bushwire.net
48618 by: David Gadoury
48620 by: Justin Bell
rcphosts
48622 by: Jerry Hsieh
48624 by: Ronny Haryanto
A few clues for linuxpeople
48623 by: Dave Sill
48634 by: Stephen Bosch
Mypoints.com is not nice to us qmail admins (was: C API for queueing messages)
48628 by: Aaron L. Meehan
48630 by: Michael Boyiazis
48686 by: Eric Cox
ok i give up, i need help...
48633 by: Chris Scheller
48636 by: Chris Johnson
48637 by: Chris Scheller
Re: qmail performance under Solaris8
48638 by: Nathan J. Mehl
48640 by: John White
48642 by: Nathan J. Mehl
48644 by: Felix von Leitner
48648 by: Nathan J. Mehl
48654 by: Felix von Leitner
48660 by: Oezguer Kesim
48667 by: Nathan J. Mehl
48669 by: Nathan J. Mehl
Lots of qmail-queue processes
48643 by: Sean Peterson
48645 by: markd.bushwire.net
48647 by: markd.bushwire.net
48652 by: Sean Peterson
48653 by: Ben Beuchler
48657 by: markd.bushwire.net
48659 by: Sean Peterson
48689 by: Andrew Richards
question about uninstall
48646 by: shawn p. duffy
48649 by: Ben Beuchler
48650 by: Nathan J. Mehl
qmail + freebsd = reboot
48651 by: Gustavo Vieira Goncalves Coelho Rios
48656 by: Tim Hunter
48665 by: Alfred Perlstein
48668 by: ynishimura.home.nimc.go.jp
48670 by: Russ Allbery
48679 by: Jonel Rienton
48680 by: Jordan Hubbard
48682 by: James T. Perry
Virtual domain Help please.
48655 by: Dejan Markic
48663 by: Oezguer Kesim
PLEASE, PLEASE : qmail is rebooting my box
48658 by: Gustavo Vieira Goncalves Coelho Rios
48666 by: Aaron L. Meehan
qmail vs ld.so & execve()
48672 by: Pavel Kankovsky
New Installation
48673 by: Ramzi S. Abdallah
48675 by: Chris Johnson
48676 by: Russ Allbery
Forward
48674 by: Ruben Curto
removing messages FROM a specific user
48677 by: Ben Beuchler
why replica lose entry ?
48678 by: Michael Y. Kim
multilog question
48683 by: James T. Perry
48685 by: markd.bushwire.net
CNAME lookup failed temporarily. (#4.4.3) - BUG In qmail-remote ?!
48688 by: Alex V. Toropov
Where i can find howto mini-qmail ?
48690 by: Michael Y. Kim
48691 by: Robin S. Socha
FAQ Listbot? (was: Re: rcphosts)
48692 by: Eric Cox
Who is the list owner/admin?
48694 by: Sarah Thompson
Re: Mypoints.com is not nice to us qmail admins (was: C API for
48695 by: Frank Tegtmeyer
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Ok everyone sorry about the posting of hundreds of lines of source code I felt that it was needed and apparently you don't. I was just being thorough. I promise its not intended to upset anyone. I swear! Also keepin mind this is the real world and I own a 486 with 8 megs of ram and a small hard drive. I did not install a compiler except to accommodate qmail on this machine. I compiled the 2.2.16 kernel on a fast machine and moved it to the 486 which is the proposed mail server. I suppose I could do the same with the qmail program but as you can tell I am not adept at this sort of thing. SO I suppose I "need" to install the kernel sources even though the files are on my drive? Why? If they are there why not move them or link them somehow? After all it seems that I am limited to the actual steps in the INSTALL docs. lesss I lose this last line of tech support. I don't want to get creative and start "doing it my way" now do I? Or you guys will just yell at me again! I can re-install the entire machine with red hat 6.0 then upgrade every package again, but I don't see the need its a fresh 112 meg install with the various applications upgraded as needed to meet security issues that have arisen as of late. I do not want to re-install the entire machine but can. I can install the kernel source and headers if needed but I am low on space. Suggestions on what to do? (I am reading the nice replys and trying them first thanks guys) ----- Original Message ----- From: "Russ Allbery" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 2:11 AM Subject: Re: linuxpeople thread > Please don't post hundreds of lines of directory listings of the qmail > source. > > [EMAIL PROTECTED] writes: > > > /compile qmail-local.c > > qmail-local.c:1: sys/types.h: No such file or directory > > qmail-local.c:2: sys/stat.h: No such file or directory > > There's something seriously wrong with your system include files; both of > those files should be in /usr/include. This is *not* a problem with your > kernel sources as another person said (if it were, sys/types.h would be > found and linux/types.h would be missing); it's a problem at an even > earlier level than that. > > Your system's development environment is either corrupted or only > partially installed at a very fundamental level. > > -- > Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> >
linuxpeople <[EMAIL PROTECTED]> writes: > I can re-install the entire machine with red hat 6.0 then upgrade every > package again, but I don't see the need its a fresh 112 meg install with > the various applications upgraded as needed to meet security issues that > have arisen as of late. My Linux box says that /usr/include/sys/types.h is part of glibc-devel. Do you have that package installed? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Am I replying correctly or are these screwing up the "threads" again? I am using outlook express and will continue to do so throughout this ordeal so if its ruining the "web page" posting please tell me now so I can do it correctly. I hit "reply all" to respond to these is that correct? **Also, please scroll down for the comments to this post, they actually worked now I have a new error. ----- Original Message ----- From: "Steve Carter" <[EMAIL PROTECTED]> To: "Qmail mailing list (E-mail)" <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 2:08 AM Subject: RE: linuxpeople thread > ... > > qmail-local.c:1: sys/types.h: No such file or directory > > qmail-local.c:2: sys/stat.h: No such file or directory > > make: *** [qmail-local.o] Error 1 > > [root@www qmail-1.03]# > > > > DARN!!! > > > > however, > > > > [root@www qmail-1.03]# locate types.h > > /usr/include/security/_pam_types.h > > /usr/i386-glibc21-linux/include/asm/kmap_types.h > > /usr/i386-glibc21-linux/include/asm/posix_types.h > > /usr/i386-glibc21-linux/include/asm/types.h > > /usr/i386-glibc21-linux/include/bits/ioctl-types.h > > /usr/i386-glibc21-linux/include/bits/pthreadtypes.h > > /usr/i386-glibc21-linux/include/bits/types.h > > /usr/i386-glibc21-linux/include/inttypes.h > > /usr/i386-glibc21-linux/include/linux/posix_types.h > > /usr/i386-glibc21-linux/include/linux/qnxtypes.h > > /usr/i386-glibc21-linux/include/linux/sunrpc/types.h > > /usr/i386-glibc21-linux/include/linux/types.h > > /usr/i386-glibc21-linux/include/nl_types.h > > /usr/i386-glibc21-linux/include/rpc/types.h > > /usr/i386-glibc21-linux/include/sys/bitypes.h > > /usr/i386-glibc21-linux/include/sys/types.h > > [root@www qmail-1.03]# > > > > and > > > > [root@www qmail-1.03]# locate stat.h > > /usr/i386-glibc21-linux/include/asm/stat.h > > /usr/i386-glibc21-linux/include/bits/stat.h > > /usr/i386-glibc21-linux/include/bits/ustat.h > > /usr/i386-glibc21-linux/include/linux/kernel_stat.h > > /usr/i386-glibc21-linux/include/linux/stat.h > > /usr/i386-glibc21-linux/include/rpcsvc/rstat.h > > /usr/i386-glibc21-linux/include/sys/stat.h > > /usr/i386-glibc21-linux/include/sys/ustat.h > > /usr/i386-glibc21-linux/include/ustat.h > > [root@www qmail-1.03]# > > > > reveals that these files are indeed on the drive someplace. > > I get this: > > bash$ locate sys/types.h > /usr/include/sys/types.h > /usr/lib/bcc/include/sys/types.h > /usr/i386-glibc20-linux/include/sys/types.h > bash$ locate sys/stat.h > /usr/include/sys/stat.h > /usr/lib/bcc/include/sys/stat.h > /usr/i386-glibc20-linux/include/sys/stat.h > bash$ > > I reckon you've got a duff linux install. If /usr/include does > not exist, try a "duff" = messed up? Or something specific? > > $ ln -s /usr/i386-glibc21-linux/include /usr/include > > if /usr/include does but /usr/include/sys doesn't, try > > $ ln -s /usr/i386-glibc21-linux/include/sys /usr/include/sys > > if _that_ exists too, try > > $ cp /usr/i386-glibc21-linux/include/sys/stat.h /usr/include/sys/ > $ cp /usr/i386-glibc21-linux/include/sys/types.h /usr/include/sys/ > Ok I think I am making progress [root@www qmail-1.03]# ln -s /usr/i386-glibc21-linux/include/sys /usr/include/sys [root@www qmail-1.03]# cp /usr/i386-glibc21-linux/include/sys/types.h /usr/include/sys/ cp: `/usr/i386-glibc21-linux/include/sys/types.h' and `/usr/include/sys/types.h' are the same file [root@www qmail-1.03]# cp /usr/i386-glibc21-linux/include/sys/stat.h /usr/include/sys/ cp: `/usr/i386-glibc21-linux/include/sys/stat.h' and `/usr/include/sys/stat.h' are the same file [root@www qmail-1.03]# make setup check /compile qmail-local.c In file included from qmail-local.c:1: /usr/include/sys/types.h:26: features.h: No such file or directory /usr/include/sys/types.h:30: bits/types.h: No such file or directory /usr/include/sys/types.h:123: time.h: No such file or directory In file included from qmail-local.c:2: /usr/include/sys/stat.h:26: features.h: No such file or directory /usr/include/sys/stat.h:28: bits/types.h: No such file or directory /usr/include/sys/stat.h:89: bits/stat.h: No such file or directory make: *** [qmail-local.o] Error 1 That looks like progress to me ... > This is what I'd do to get going and try qmail out, but I'd try to > get to the bottom of why you don't have /usr/include/sys/types.h in > the first place. Me too! > What linux distribution are you using? Red Hat 6.0 with all www related security updates including a 2.2.16 kernel I compiled on another machine and transferred over. > > > got verbally and mentally abused by the entire world for being > > "so fscking like the GNU generation" or some such nonsense. > > Relax about that; the majority of folks on this list don't hold that > poster's opinion, or if they do, they're a bit more patient... > Ok thanks : ) maybe I can sleep now
Unfortunately you can't. "lusers" like you and me are spoiling it for everyone. We should get new MUAs. ("mail clients") > I am using outlook express and will continue to do so > throughout this ordeal so if its ruining the "web page" > posting please tell me now so I can do it correctly.
----- Original Message ----- From: "Russ Allbery" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 3:14 AM Subject: Re: linuxpeople thread > linuxpeople <[EMAIL PROTECTED]> writes: > > > I can re-install the entire machine with red hat 6.0 then upgrade every > > package again, but I don't see the need its a fresh 112 meg install with > > the various applications upgraded as needed to meet security issues that > > have arisen as of late. > > My Linux box says that /usr/include/sys/types.h is part of glibc-devel. > Do you have that package installed? error: failed dependencies: kernel-headers is needed by glibc-devel-2.1.3-15 kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 Apparently not. I will install glibc-devel-2.1.3-15 and its deps right now if you think it will help. I have a feeling I will just be a lot lower on disk space after this. After all I have those .h files its looking for on the drive now. What I do not have is a need for a full fledged "development" installation. This is a 486 with 8 megs of ram on a 500 meg hard drive and the less compiling and un-needed installations I do the better. so at great distress I post these lines : [root@www qmail-1.03]# make setup check /compile qmail-local.c In file included from qmail-local.c:1: /usr/include/sys/types.h:26: features.h: No such file or directory /usr/include/sys/types.h:30: bits/types.h: No such file or directory /usr/include/sys/types.h:123: time.h: No such file or directory In file included from qmail-local.c:2: /usr/include/sys/stat.h:26: features.h: No such file or directory /usr/include/sys/stat.h:28: bits/types.h: No such file or directory /usr/include/sys/stat.h:89: bits/stat.h: No such file or directory make: *** [qmail-local.o] Error 1 I am sorry I included so many but I think you need them all. Ok those files are also on the hard drive. They are all in /usr/i386-glibc21-linux/include/ and I tried cp *.h /usr/include/sys Now they are all in there but "make setup check" still gives the same error. I got this far by trying what Steve Carter suggested earlier. He may have replied by now. I realize this is not a qmail problem, rather a small - install problem and do appreciate any help offered > > -- > Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> >
linuxpeople <[EMAIL PROTECTED]> writes: > error: failed dependencies: > kernel-headers is needed by glibc-devel-2.1.3-15 > kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 > > Apparently not. > > I will install glibc-devel-2.1.3-15 and its deps right now if you think it > will help. Wouldn't it just be possible to: 1) do everything in the INSTALL on a ``faster'' development machine, 2) tar up the source tree with the binaries already built, 3) transfer it to the less-disk-endowed machine, 4) untar it, and 5) run make setup check? All of this without requiring a compiler on the lesser machine...doable? (For that matter, ``linuxpeople'', you should be able to build a binary RPM from the source RPM on the faster machine and use that binary to install on the lesser machine.) Obligatory support note: people on this list tend to get a little cranky. Why? Because this is NOT a Linux, Redhat, gcc, RPM, &c. support list. You would note that the RPM stuff isn't standard by looking at <http://cr.yp.to/qmail.html> and noting that there is no mention of RPMs there. The FAQ located at that page mentions nothing about RPMs. If you are receiving compiler errors, the first thing to check is *your* *compiler*, NOT the application you are trying to compile. If you are uncertain as to how compilers work (even at a very rudimentary level, as is the extent of my knowledge), you should ask on a OS-specific mailing list what you're doing wrong. (You might even consider another line of work, or doing a whole lot of reading on computers before you continue. Trust me, this will save you headaches, even those given to you by ``rude'' people on mailing lists.) Finally, if you *still* had questions on the RPM install (sorry I'm harping on it, but I've used it extensively, and I *love* it), you probably ought to have read the page from which you downloaded the RPM. <http://em.ca/~bruceg/qmail+patches/> ``If you have any comments or requests, please e-mail me at [EMAIL PROTECTED]'' ``A mailing list has been set up to discuss these RPMs. To subscribe, send an email to: [EMAIL PROTECTED]'' Bruce and the others on that list would quickly point you to this list if the problem were truly related to qmail, which it isn't. /pg, who accepts Visa/Mastercard for long support posts. -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- "And the next time you consider complaining that running Lucid Emacs 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to get the background colors right, you'll know who to thank." (By Matt Welsh)
----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Russ Allbery" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 4:37 AM Subject: Re: linuxpeople thread > > ----- Original Message ----- > From: "Russ Allbery" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, September 13, 2000 3:14 AM > Subject: Re: linuxpeople thread > > > > linuxpeople <[EMAIL PROTECTED]> writes: > > > > > I can re-install the entire machine with red hat 6.0 then upgrade every > > > package again, but I don't see the need its a fresh 112 meg install with > > > the various applications upgraded as needed to meet security issues that > > > have arisen as of late. > > > > My Linux box says that /usr/include/sys/types.h is part of glibc-devel. > > Do you have that package installed? Thanks Russ Allbery, I installed glibc-devel and its deps, and watched it make the proper files and directories. I also lost 40 megs of disk space! There is no way I can use this on my normal 200 meg hard drive, 486 server installs .. its a shame. But its compiling! Judging by the speed of the first 10 lines I am should try and sleep while it finishes, but thats not going to happen. Thanks for taking the time to check that for me you basically solved the problem.now. I can go on to step 4 woo hooo! > > error: failed dependencies: > kernel-headers is needed by glibc-devel-2.1.3-15 > kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 > > Apparently not. > > I will install glibc-devel-2.1.3-15 and its deps right now if you think it > will help. > > I have a feeling I will just be a lot lower on disk space after this. After > all I have those .h files its looking for on the drive now. > > What I do not have is a need for a full fledged "development" installation. > This is a 486 with 8 megs of ram on a 500 meg hard drive and the less > compiling and un-needed installations I do the better. > > so at great distress I post these lines : > > [root@www qmail-1.03]# make setup check > /compile qmail-local.c > In file included from qmail-local.c:1: > /usr/include/sys/types.h:26: features.h: No such file or directory > /usr/include/sys/types.h:30: bits/types.h: No such file or directory > /usr/include/sys/types.h:123: time.h: No such file or directory > In file included from qmail-local.c:2: > /usr/include/sys/stat.h:26: features.h: No such file or directory > /usr/include/sys/stat.h:28: bits/types.h: No such file or directory > /usr/include/sys/stat.h:89: bits/stat.h: No such file or directory > make: *** [qmail-local.o] Error 1 > > I am sorry I included so many but I think you need them all. > > Ok those files are also on the hard drive. They are all in > /usr/i386-glibc21-linux/include/ > > and I tried cp *.h /usr/include/sys Now they are all in there but "make > setup check" still gives the same error. > > I got this far by trying what Steve Carter suggested earlier. He may have > replied by now. > > I realize this is not a qmail problem, rather a small - install problem and > do appreciate any help offered > > > > > > > -- > > Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> > > >
----- Original Message ----- From: "Peter Green" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 5:13 AM Subject: Re: linuxpeople thread > linuxpeople <[EMAIL PROTECTED]> writes: > > error: failed dependencies: > > kernel-headers is needed by glibc-devel-2.1.3-15 > > kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 > > > > Apparently not. > > > > I will install glibc-devel-2.1.3-15 and its deps right now if you think it > > will help. > > Wouldn't it just be possible to: > > 1) do everything in the INSTALL on a ``faster'' development machine, > 2) tar up the source tree with the binaries already built, > 3) transfer it to the less-disk-endowed machine, > 4) untar it, and > 5) run make setup check? Obviously, I even suggested that. However, its not mentioned in the qmail docs as "acceptable" to do so. > All of this without requiring a compiler on the lesser machine...doable? > (For that matter, ``linuxpeople'', you should be able to build a binary RPM Is that a slam against the name "linuxpeople"? > from the source RPM on the faster machine and use that binary to install on > the lesser machine.) Why should I have to go through that bother? The qmail page provides a link to an RPM for red hat in the first paragraph. http://www.qmail.org/top.html SRC RPMS are as much of a hassle as compiling and moving qmail/ You know, nearly everyones response has been "you should have read this or that" well I am here to tell you I do read very well, and have read all available docs for 4 days. The docs can not possibly cover every situation, and did not cover mine! Reading is a lot easier then dealing with antosocial-newbie-haters that wish they were part of the l33t that run Internet but are stuck volunteering on a free software maill support list, so they pick on every obvious newbie that asks a question. > Obligatory support note: people on this list tend to get a little cranky. Yeah right ... and some people are emotionally disturbed and should not be helping with this list at all. That guy from earlier needs extensive counseling for his problems. Thank god all I need is a faster machine with a newer distro and a line in my ipchains ipchains -A output -d kens.com -j REJECT > Why? Because this is NOT a Linux, Redhat, gcc, RPM, &c. support list. I never claimed it was, I initially asked questions about a running install of qmail that had errors. I was told to re-install from source (among other less-helpful suggestions) for the best effect, and that people might be able to help with the error I mentioned. It is already done compiling now. I sure as hell hope the docs cover runnig and maintaing qmail better than they do the installation. Like I said in this post you are replying to "I realize this is not a qmail problem, rather a small - install problem and do appreciate any help offered" Who needs to read more closely? >You would note that the RPM stuff isn't standard by looking at > <http://cr.yp.to/qmail.html> and noting that there is no mention of RPMs the link to the RPM is on the qmail page http://www.qmail.org/top.html so I suggest someone quit linking it or post a warning that you will be ridiculed and/or ignored by the qmail crew if you use it! > there. The FAQ located at that page mentions nothing about RPMs. If you are > receiving compiler errors, the first thing to check is *your* *compiler*, **obviously, as I have stated many times myself ...** > NOT the application you are trying to compile. **How many times must I mention that I know that its not qmail ?** > If you are uncertain as to > how compilers work (even at a very rudimentary level, as is the extent of my > knowledge), you should ask on a OS-specific mailing list what you're doing > wrong. (You might even consider another line of work, or doing a whole lot > of reading on computers before you continue. Trust me, this will save you > headaches, even those given to you by ``rude'' people on mailing lists.) Geez you would no fun at a pep rally and please do not take work as an inspiration speaker! > Finally, if you *still* had questions on the RPM install (sorry I'm harping > on it, but I've used it extensively, what the rpm? >and I *love* it), you probably ought to > have read the page from which you downloaded the RPM. there you go again accusing me of not reading .. believe me this list is a last resort! Not only did I read the every doc I could find online I install with rpm -ivvh --test and read all that output. > <http://em.ca/~bruceg/qmail+patches/> > ``If you have any comments or requests, please e-mail me at [EMAIL PROTECTED]'' > ``A mailing list has been set up to discuss these RPMs. To subscribe, send > an email to: [EMAIL PROTECTED]'' Ok in my case the rpms did not make the "qmail-smtp" plain and simple, if you read back you will see the thread someplace in this mess. If you like I can duplicate this on another 486 when I am done with this. I know it will happen again as I always use the same install. Base red hat of 112 megs, then I add packages later as needed. Ok you must mean the RPM I dunno man. After that pep talk are you going to try to sell me the latest version of MS Outlook? > Bruce and the others on that list would quickly point you to this list if > the problem were truly related to qmail, which it isn't. I don't quite understand that last bit ... but I know the problem is me and my 8 meg 486 with a 500 meg hard drive running red hat 6.0 It is a very unsual machine the only one like it in the world right? > > /pg, who accepts Visa/Mastercard for long support posts. Hilarious > -- > Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] > --- > "And the next time you consider complaining that running Lucid Emacs > 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to > get the background colors right, you'll know who to thank." > (By Matt Welsh) Hilarious > > well since make setup check worked I am off to go: 4. Read INSTALL.ctl and FAQ. Minimal survival command: # ./config later
On Wed, Sep 13, 2000 at 06:01:26AM -0700, [EMAIL PROTECTED] wrote: > Reading is a lot easier then dealing with antosocial-newbie-haters that wish > they were part of the l33t that run Internet but are stuck volunteering on a > free software maill support list, so they pick on every obvious newbie that > asks a question. "Stuck volunteering" is an oxymoron. You're one of the more annoying people who's posted on this list in a while. Most newbies manage to post their questions and get answers here without pissing everyone off. > Yeah right ... and some people are emotionally disturbed and should not be > helping with this list at all. That guy from earlier needs extensive > counseling for his problems. Good luck getting any more help. You're on your own now. Chris
----- Original Message ----- From: "Chris Johnson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 6:25 AM Subject: Re: linuxpeople thread > On Wed, Sep 13, 2000 at 06:01:26AM -0700, [EMAIL PROTECTED] wrote: > > Reading is a lot easier then dealing with antosocial-newbie-haters that wish > > they were part of the l33t that run Internet but are stuck volunteering on a > > free software maill support list, so they pick on every obvious newbie that > > asks a question. > > "Stuck volunteering" is an oxymoron. > > You're one of the more annoying people who's posted on this list in a while. > Most newbies manage to post their questions and get answers here without > pissing everyone off. > > > Yeah right ... and some people are emotionally disturbed and should not be > > helping with this list at all. That guy from earlier needs extensive > > counseling for his problems. > > Good luck getting any more help. You're on your own now. Now? Where have you been? As far as pissing people off that seems to be the main goal of the peole that have replied to my posts. I know all you guys are not like this, but most of you seem to be. Why waste the time? When a newbie comes to me for help I pay special attention to their needs and do not simply reply with "RTFM" or "man this" like most of the "help" out there. My question is this Chris, "Why did you even bother replying it has nothing to do with my problem with qmail? Thanks for nothing. I see its ok for that kens.net guy to call me names like "STUPID" and "luser" and even change the name of my thread to "linuxluser" all because he assmes I didn't read anything especially his reply ...which had not yet arrived when he flamed me. But I can't call him like I see him? That guy needs professional counseling and I sure hope he gets it. This support list is somewhat of a joke as I suspected it would be. The worst part is years from now when people come across the thread, he will still be attacking people and I will be helping them. > > Chris >
I got all the way up to: Step 7. Read INSTALL.maildir Here's how to set up qmail to use maildir for your incoming mail: % maildirmake $HOME/Maildir % echo ./Maildir/ > ~/.qmail [root@www qmail-1.03]# maildirmake $HOME/Maildir bash: maildirmake: command not found [root@www qmail-1.03]# Any legitimate suggestions? A NOTE for the kiddies in here .. Frankly, I would prefer if the emotionally insecure to just ignore my posts ok? The people that didn't make fun of me actually answered my questions. qmail is installed now. Coincidence? If you don't know the answer to my questions then please stfu about it and keep your opinion to yourself for once in your life. If you think you can belittle me and expect to me to sit back and take it forever then you have another thing coming! This is the last post including any notes of a personal nature. If you have a problem or want to call me names then email me directly.
try /var/qmail/bin/maildirmake $HOME/Maildir don't run it as root either, run it as a user, qmail does not run or deliver as root it will just screw up your maildir permissions. Have your read Life with qmail by Dave Sill? It seems to be the just the documentation you need, there is a link to it from the qmail.org site. -- Tim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 13, 2000 10:01 AM To: Steve Carter; Qmail mailing list (E-mail) Subject: Re: linuxpeople thread I got all the way up to: Step 7. Read INSTALL.maildir Here's how to set up qmail to use maildir for your incoming mail: % maildirmake $HOME/Maildir % echo ./Maildir/ > ~/.qmail [root@www qmail-1.03]# maildirmake $HOME/Maildir bash: maildirmake: command not found [root@www qmail-1.03]# Any legitimate suggestions? A NOTE for the kiddies in here .. Frankly, I would prefer if the emotionally insecure to just ignore my posts ok? The people that didn't make fun of me actually answered my questions. qmail is installed now. Coincidence? If you don't know the answer to my questions then please stfu about it and keep your opinion to yourself for once in your life. If you think you can belittle me and expect to me to sit back and take it forever then you have another thing coming! This is the last post including any notes of a personal nature. If you have a problem or want to call me names then email me directly.
On Mit, 13 Sep 2000, [EMAIL PROTECTED] wrote: > I got all the way up to: > Step 7. > Read INSTALL.maildir > > Here's how to set up qmail to use maildir for your incoming mail: > > % maildirmake $HOME/Maildir > % echo ./Maildir/ > ~/.qmail > > [root@www qmail-1.03]# maildirmake $HOME/Maildir > bash: maildirmake: command not found > [root@www qmail-1.03]# > > Any legitimate suggestions? Seems you haven't got /var/qmail/bin in your path. Try /var/qmail/bin/maildirmake $HOME/Maildir hih, -- Oliver Koch Systems Administrator Computational Mathematics & Optimization Institute of Analysis Johannes Kepler University Linz Austria [EMAIL PROTECTED] Tel. +43 70 2469 9166
Thus spake [EMAIL PROTECTED] ([EMAIL PROTECTED]): > [root@www qmail-1.03]# maildirmake $HOME/Maildir > bash: maildirmake: command not found > [root@www qmail-1.03]# > > Any legitimate suggestions? /var/qmail/bin/maildirmake or PATH=$PATH:/var/qmail/bin maildirmake I prefer learning the basics of a UNIX environment first before trying to setup qmail. oec
> % maildirmake $HOME/Maildir > % echo ./Maildir/ > ~/.qmail > > [root@www qmail-1.03]# maildirmake $HOME/Maildir > bash: maildirmake: command not found > [root@www qmail-1.03]# > > Any legitimate suggestions? It's not in your path, so specify the path to it jason
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 09:54]: > "Chris Johnson" <[EMAIL PROTECTED]> > > You're one of the more annoying people who's posted on this list in > > a while. Most newbies manage to post their questions and get > > answers here without pissing everyone off. [...] > > Good luck getting any more help. You're on your own now. > > Now? Where have you been? As far as pissing people off that seems to > be the main goal of the peole that have replied to my posts. Doesn't that make you wonder why? > This support list is ... not a support list: |qmail: For discussion of the qmail package, the qmailanalog package, the |dot-forward package, and the fastforward package. To subscribe, send an |empty message to [EMAIL PROTECTED] This list is unmoderated |and high-volume. What you were looking for can be found here: http://cr.yp.to/qmail/faq/solutions.html > The worst part is years from now when people come across the thread, > he will still be attacking people and I will be helping them. Yeah, right: "Nameless idiot helps ML reader to death after being flamed by a Bastard." Film at 11. Anyone feel like buying popcorn shares?
On 13 00, [EMAIL PROTECTED] wrote: # I got all the way up to: # Step 7. # Read INSTALL.maildir # # Here's how to set up qmail to use maildir for your incoming mail: # # % maildirmake $HOME/Maildir # % echo ./Maildir/ > ~/.qmail # # [root@www qmail-1.03]# maildirmake $HOME/Maildir # bash: maildirmake: command not found # [root@www qmail-1.03]# # # Any legitimate suggestions? # learn how to use your OS before you try to install an MTA? Do you know what a PATH environment setting is? do you not know how to find a file? eg find / -name maildirmake which *should* be in /var/qmail/bin then issue the command /var/qmail/bin/maildirmake
[EMAIL PROTECTED] wrote: > > so at great distress I post these lines : > > [root@www qmail-1.03]# make setup check > /compile qmail-local.c > In file included from qmail-local.c:1: > /usr/include/sys/types.h:26: features.h: No such file or directory > /usr/include/sys/types.h:30: bits/types.h: No such file or directory > /usr/include/sys/types.h:123: time.h: No such file or directory > In file included from qmail-local.c:2: > /usr/include/sys/stat.h:26: features.h: No such file or directory > /usr/include/sys/stat.h:28: bits/types.h: No such file or directory > /usr/include/sys/stat.h:89: bits/stat.h: No such file or directory > make: *** [qmail-local.o] Error 1 > > I am sorry I included so many but I think you need them all. > > Ok those files are also on the hard drive. They are all in > /usr/i386-glibc21-linux/include/ They're not the same files =( Are you really sure you want the misery of running a mail server on a 486 with only 8 Mb of RAM? -Stephen-
> Yeah, right: "Nameless idiot helps ML reader to death after being flamed > by a Bastard." Film at 11. Anyone feel like buying popcorn shares? I suggest that everyone who feels that linuxpeople is stupid should ignore him NOW. Everyone who thinks there is any hope he will get his system up should support him by private mail NOW. Hopefully it will kill this idiotic thread fast. Regards, Frank
the more you whine, complain, bitch, act like a bitch etc, the more you will be ignored, ridiculed, tormented and abused. stop your whining and suck it up. welcome to the real internet. on the other hand you can always ignore those who bug you. filter the offender to /dev/null and have the last laugh ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Peter Green" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 8:01 AM Subject: Re: linuxpeople thread > ----- Original Message ----- > From: "Peter Green" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, September 13, 2000 5:13 AM > Subject: Re: linuxpeople thread > > > > linuxpeople <[EMAIL PROTECTED]> writes: > > > error: failed dependencies: > > > kernel-headers is needed by glibc-devel-2.1.3-15 > > > kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 > > > > > > Apparently not. > > > > > > I will install glibc-devel-2.1.3-15 and its deps right now if you think > it > > > will help. > > > > Wouldn't it just be possible to: > > > > 1) do everything in the INSTALL on a ``faster'' development machine, > > 2) tar up the source tree with the binaries already built, > > 3) transfer it to the less-disk-endowed machine, > > 4) untar it, and > > 5) run make setup check? > > Obviously, I even suggested that. However, its not mentioned in the qmail > docs as "acceptable" to do so. > > > All of this without requiring a compiler on the lesser machine...doable? > > (For that matter, ``linuxpeople'', you should be able to build a binary > RPM > > Is that a slam against the name "linuxpeople"? > > > from the source RPM on the faster machine and use that binary to install > on > > the lesser machine.) > > Why should I have to go through that bother? The qmail page provides a link > to an RPM for red hat in the first paragraph. http://www.qmail.org/top.html > SRC RPMS are as much of a hassle as compiling and moving qmail/ > > You know, nearly everyones response has been "you should have read this or > that" well I am here to tell you I do read very well, and have read all > available docs for 4 days. The docs can not possibly cover every situation, > and did not cover mine! Reading is a lot easier then dealing with > antosocial-newbie-haters that wish they were part of the l33t that run > Internet but are stuck volunteering on a free software maill support list, > so they pick on every obvious newbie that asks a question. > > > Obligatory support note: people on this list tend to get a little cranky. > > Yeah right ... and some people are emotionally disturbed and should not be > helping with this list at all. That guy from earlier needs extensive > counseling for his problems. Thank god all I need is a faster machine with > a newer distro and a line in my ipchains > > ipchains -A output -d kens.com -j REJECT > > > Why? Because this is NOT a Linux, Redhat, gcc, RPM, &c. support list. > > I never claimed it was, I initially asked questions about a running install > of qmail that had errors. I was told to re-install from source (among other > less-helpful suggestions) for the best effect, and that people might be able > to help with the error I mentioned. It is already done compiling now. I > sure as hell hope the docs cover runnig and maintaing qmail better than they > do the installation. > > Like I said in this post you are replying to "I realize this is not a qmail > problem, rather a small - install problem and > do appreciate any help offered" Who needs to read more closely? > > >You would note that the RPM stuff isn't standard by looking at > > <http://cr.yp.to/qmail.html> and noting that there is no mention of RPMs > > the link to the RPM is on the qmail page http://www.qmail.org/top.html so I > suggest someone quit linking it or post a warning that you will be ridiculed > and/or ignored by the qmail crew if you use it! > > > there. The FAQ located at that page mentions nothing about RPMs. If you > are > > receiving compiler errors, the first thing to check is *your* *compiler*, > > **obviously, as I have stated many times myself ...** > > > NOT the application you are trying to compile. > > **How many times must I mention that I know that its not qmail ?** > > > If you are uncertain as to > > how compilers work (even at a very rudimentary level, as is the extent of > my > > knowledge), you should ask on a OS-specific mailing list what you're doing > > wrong. (You might even consider another line of work, or doing a whole lot > > of reading on computers before you continue. Trust me, this will save you > > headaches, even those given to you by ``rude'' people on mailing lists.) > > > Geez you would no fun at a pep rally and please do not take work as an > inspiration speaker! > > > Finally, if you *still* had questions on the RPM install (sorry I'm > harping > > on it, but I've used it extensively, > > what the rpm? > > >and I *love* it), you probably ought to > > have read the page from which you downloaded the RPM. > > there you go again accusing me of not reading .. believe me this list is a > last resort! Not only did I read the every doc I could find online I > install with rpm -ivvh --test and read all that output. > > > <http://em.ca/~bruceg/qmail+patches/> > > ``If you have any comments or requests, please e-mail me at > [EMAIL PROTECTED]'' > > ``A mailing list has been set up to discuss these RPMs. To subscribe, send > > an email to: [EMAIL PROTECTED]'' > > Ok in my case the rpms did not make the "qmail-smtp" plain and simple, if > you read back you will see the thread someplace in this mess. If you like I > can duplicate this on another 486 when I am done with this. I know it will > happen again as I always use the same install. Base red hat of 112 megs, > then I add packages later as needed. > > Ok you must mean the RPM I dunno man. After that pep talk are you going > to try to sell me the latest version of MS Outlook? > > > Bruce and the others on that list would quickly point you to this list if > > the problem were truly related to qmail, which it isn't. > > I don't quite understand that last bit ... but I know the problem is me and > my 8 meg 486 with a 500 meg hard drive running red hat 6.0 It is a very > unsual machine the only one like it in the world right? > > > > > /pg, who accepts Visa/Mastercard for long support posts. > > Hilarious > > > -- > > Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] > > --- > > "And the next time you consider complaining that running Lucid Emacs > > 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to > > get the background colors right, you'll know who to thank." > > (By Matt Welsh) > > Hilarious > > > > > > well since make setup check worked > I am off to go: > > 4. Read INSTALL.ctl and FAQ. Minimal survival command: > # ./config > > > later
> > Any legitimate suggestions? yeah several, but this is a qmail list not a general-unix-help list so figure it out yourself.
----- Original Message ----- From: "Robin S. Socha" <[EMAIL PROTECTED]> > > Now? Where have you been? As far as pissing people off that seems to > > be the main goal of the peole that have replied to my posts. > > Doesn't that make you wonder why? > > Yeah, right: "Nameless idiot helps ML reader to death after being flamed > by a Bastard." Film at 11. Anyone feel like buying popcorn shares? You just have a bad attitude, plain and simple. And like I said in private before, you've come close to prosecutable offenses in some countries. Note: your posts are more noise, less signal, than any of the people you've flamed. Most of my flames are done in private Email. Start reading some of those Internet newbie sites again, and learn how to deal with people you don't like on mailing lists the recommended way -- in private. I think you just enjoy being heard (anyone want to search 'socha' in the mail archives?). Note: which part of "discussion of qmail" eliminates asking for help? Its not a specific help list, no. Its a _general_ list.
Thus spake Stephen Bosch ([EMAIL PROTECTED]): > [EMAIL PROTECTED] wrote: > > so at great distress I post these lines : > > > > [root@www qmail-1.03]# make setup check > > /compile qmail-local.c > > In file included from qmail-local.c:1: > > /usr/include/sys/types.h:26: features.h: No such file or directory > > /usr/include/sys/types.h:30: bits/types.h: No such file or directory > > /usr/include/sys/types.h:123: time.h: No such file or directory > > In file included from qmail-local.c:2: > > /usr/include/sys/stat.h:26: features.h: No such file or directory > > /usr/include/sys/stat.h:28: bits/types.h: No such file or directory > > /usr/include/sys/stat.h:89: bits/stat.h: No such file or directory > > make: *** [qmail-local.o] Error 1 > > > > I am sorry I included so many but I think you need them all. > > > > Ok those files are also on the hard drive. They are all in > > /usr/i386-glibc21-linux/include/ [to "[EMAIL PROTECTED]": (I just joined and didn't get the original posting)] Fix your fucking system. Oh, and learn how to cut and paste. The first line starts with "./compile", not "/compile". Alternatively, you might edit compile to include "-I/usr/i386-glibc21-linux/include", but then linking will probably fail. I will tell you how to fix that for my low, low rate of $ 1000 a minute. Additional fees may apply. > Are you really sure you want the misery of running a mail server on a > 486 with only 8 Mb of RAM? I once ran a mail server with server high volume mailing lists on a 386 with 4 Megs RAM. It lasted several months, before we replaced it to get higher response times from the web server that was also running on the box. Felix
[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes on 13 September 2000 at 04:37:19 -0700 > > ----- Original Message ----- > From: "Russ Allbery" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, September 13, 2000 3:14 AM > Subject: Re: linuxpeople thread > > > > linuxpeople <[EMAIL PROTECTED]> writes: > > > > > I can re-install the entire machine with red hat 6.0 then upgrade every > > > package again, but I don't see the need its a fresh 112 meg install with > > > the various applications upgraded as needed to meet security issues that > > > have arisen as of late. > > > > My Linux box says that /usr/include/sys/types.h is part of glibc-devel. > > Do you have that package installed? > > error: failed dependencies: > kernel-headers is needed by glibc-devel-2.1.3-15 > kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 > > Apparently not. > > I will install glibc-devel-2.1.3-15 and its deps right now if you think it > will help. Yes, it will. The "devel" variant of glibc is needed if you intend to compile software, essentially any software, on your system. Which is exactly what you're trying to do. (I'm running Redhat 6.2, with qmail build from the source tarball.) > I have a feeling I will just be a lot lower on disk space after this. After > all I have those .h files its looking for on the drive now. > > What I do not have is a need for a full fledged "development" installation. > This is a 486 with 8 megs of ram on a 500 meg hard drive and the less > compiling and un-needed installations I do the better. Yep, that's going to be tight. Especially memory. I ran a 486/100 with 48 meg of ram for a while recently. But my first qmail install was on a 386/25 with 8 meg of ram, and that ran for years, doing mail and web too, at my friendly local ISP. So you should be able to make it work. -- Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
Peter Green <[EMAIL PROTECTED]> writes on 13 September 2000 at 08:13:23 -0400 > linuxpeople <[EMAIL PROTECTED]> writes: > > error: failed dependencies: > > kernel-headers is needed by glibc-devel-2.1.3-15 > > kernel-headers >= 2.2.1 is needed by glibc-devel-2.1.3-15 > > > > Apparently not. > > > > I will install glibc-devel-2.1.3-15 and its deps right now if you think it > > will help. > > Wouldn't it just be possible to: > > 1) do everything in the INSTALL on a ``faster'' development machine, > 2) tar up the source tree with the binaries already built, > 3) transfer it to the less-disk-endowed machine, > 4) untar it, and > 5) run make setup check? Gotta make sure the UIDs and GIDs needed for qmail are the same on both machines. I *think* it'll work; unless there's something strange in the makefiles. The file dates within the qmail tree should be the same, so nothing *there* would trigger a recompile.... (Oh, and of course he has to have make installed, but he's got that already). It also assumes he *has* a faster and more capacious development system available. -- Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
Stephen Bosch <[EMAIL PROTECTED]> writes on 13 September 2000 at 08:55:01 -0600 > Are you really sure you want the misery of running a mail server on a > 486 with only 8 Mb of RAM? I ran one on a 386 with 8 Mb of RAM that also ran web. Worked fine, except that kernel builds were a bit slow (this being back before loadable modules in Linux, so I really had to build custom kernels). I ran smail on it for a while, and then qmail quite early (might have been as old as 0.72, don't remember for sure). Obviously it won't handle very high email loads; but it works just fine for a light load. With lots of people having DSL and cable modems, it seems to me that there's probably a renaissance in making 486-based servers going on just now :-). I had one myself until recently -- my backup dns. Finally replaced with something way over-built for the job that became available (dual Pentium Pro, 192 meg ram). -- Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
also sprach linuxpeople: > > Wouldn't it just be possible to: > > > > 1) do everything in the INSTALL on a ``faster'' development machine, > > 2) tar up the source tree with the binaries already built, > > 3) transfer it to the less-disk-endowed machine, > > 4) untar it, and > > 5) run make setup check? > > Obviously, I even suggested that. Did you try it? To what effect? > > All of this without requiring a compiler on the lesser machine...doable? > > (For that matter, ``linuxpeople'', you should be able to build a binary RPM > > Is that a slam against the name "linuxpeople"? Not at all, you didn't provide a name, I wished to address you by your ``Christian'' name, so I used the only thing you did provide. Relax a little. > > from the source RPM on the faster machine and use that binary to install on > > the lesser machine.) > > Why should I have to go through that bother? Um, because your system wasn't working and you want it to work? ``I want to be a cool Linux dude, but I don't want to go through the bother of actually learning anything. What should I do?'' > The qmail page provides a link > to an RPM for red hat in the first paragraph. http://www.qmail.org/top.html > SRC RPMS are as much of a hassle as compiling and moving qmail/ Get used to it. System administration is, in general, a hassle. > You know, nearly everyones response has been "you should have read this or > that" well I am here to tell you I do read very well, and have read all > available docs for 4 days. The docs can not possibly cover every situation, > and did not cover mine! Reading is a lot easier then dealing with > antosocial-newbie-haters that wish they were part of the l33t that run > Internet but are stuck volunteering on a free software maill support list, > so they pick on every obvious newbie that asks a question. I, for one, did not pick on you in the least. And yet, you attack me, like the clueless luser you now show yourself to be. Lighten up, and try not to get so agitated over every little thing. > > Why? Because this is NOT a Linux, Redhat, gcc, RPM, &c. support list. > > I never claimed it was, I initially asked questions about a running install > of qmail that had errors. I was told to re-install from source (among other > less-helpful suggestions) for the best effect, and that people might be able > to help with the error I mentioned. It is already done compiling now. I > sure as hell hope the docs cover runnig and maintaing qmail better than they > do the installation. Interestingly, by following the docs, I have *never* *ever* had these problems that you are experiencing. While I am sorry to hear that you are having these problems, I would hardly fault the docs. > Like I said in this post you are replying to "I realize this is not a qmail > problem, rather a small - install problem and > do appreciate any help offered" Who needs to read more closely? Like I can follow your incessant abuse and ranting...mostly, I skipped your posts because they were devoid of *useful* debugging information. > > NOT the application you are trying to compile. > > **How many times must I mention that I know that its not qmail ?** How many times must you post on the qmail list mentioning that you know that its not qmail? > > If you are uncertain as to > > how compilers work (even at a very rudimentary level, as is the extent of my > > knowledge), you should ask on a OS-specific mailing list what you're doing > > wrong. (You might even consider another line of work, or doing a whole lot > > of reading on computers before you continue. Trust me, this will save you > > headaches, even those given to you by ``rude'' people on mailing lists.) > > Geez you would no fun at a pep rally and please do not take work as an > inspiration speaker! Ha. A comedian. I was just giving a little ``tough love'' advice that you need to invest a whole lot more personal time in understanding how your system works in general if you *ever* hope to be successful as a sysadmin. > > Finally, if you *still* had questions on the RPM install (sorry I'm harping > > on it, but I've used it extensively, > > what the rpm? Yes, Bruce Guenter's qmail+patches RPM. > >and I *love* it), you probably ought to > > have read the page from which you downloaded the RPM. > > there you go again accusing me of not reading .. believe me this list is a > last resort! Not only did I read the every doc I could find online I > install with rpm -ivvh --test and read all that output. Did you read the part about asking on the rpms mailing list about the qmail RPMs? (That is, ask THAT list about the qmail RPMs, and NOT this one.) > Ok you must mean the RPM I dunno man. After that pep talk are you going > to try to sell me the latest version of MS Outlook? Well, if you can't make it as a sysadmin, you can probably get work on the comedy circuit... > > Bruce and the others on that list would quickly point you to this list if > > the problem were truly related to qmail, which it isn't. > > I don't quite understand that last bit ... What, that the problem isn't related to qmail? Why don't you try compiling something else and try to figure out how qmail is preventing you from compiling THAT program as well? When you realize that qmail has nothing to do with that problem, you might be able to figure out how qmail has nothing to do with the problem you posted about. /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- During the Middle Ages, probably one of the biggest mistakes was not putting on your armor because you were 'just going down to the corner.' (Jack Handey)
In the immortal words of [EMAIL PROTECTED] ([EMAIL PROTECTED]): > I got all the way up to: > Step 7. > Read INSTALL.maildir > > Here's how to set up qmail to use maildir for your incoming mail: > > % maildirmake $HOME/Maildir > % echo ./Maildir/ > ~/.qmail > > [root@www qmail-1.03]# maildirmake $HOME/Maildir > bash: maildirmake: command not found > [root@www qmail-1.03]# > > Any legitimate suggestions? Legitimate suggestion: put /var/qmail/bin in your $PATH, and then try again. And before people start jumping all over him for _this_, please recall that this is _exactly_ why several long-term list members have had long-standing beefs with djb over his use of an installation path which is not only nonstandard by which actively breaks standard unix failsystem assumptions. -n ------------------------------------------------------------<[EMAIL PROTECTED]> I'm getting laid tonight, so that takes precidence over the Newton, but I'll try and squeeze in some time for Nathan during the afterglow. (--Lamont Lucas) <http://www.blank.org/memory/>------------------------------------------------
In the immortal words of Michael T. Babcock ([EMAIL PROTECTED]): > > Note: your posts are more noise, less signal, than any of the people you've > flamed. Most of my flames are done in private Email. Start reading some of > those Internet newbie sites again, and learn how to deal with people you > don't like on mailing lists the recommended way -- in private. This is basically what happens when people read the BOFH stories and forget that the BOFH is a fictional character, created as a joke, and that Simon, in real life, is a reasonably well-adjusted person who is a professional on work hours and pleasant in public. As one of the co-administrators of BOFHnet, I find the emergency of such "BOFH-wannabees" pretty amusing. They will be tolerated for exactly as long as there is a labor shortage in this industry. When the hiring crunch ends, they will either learn to behave like professionals, or they will learn to flip burgers. Frankly, this industry will win in either case. -n ------------------------------------------------------<[EMAIL PROTECTED]> "Dude, don't say 'pigfucker' in front of Jesus!" <http://www.blank.org/memory/>------------------------------------------
Frank Tegtmeyer <[EMAIL PROTECTED]> writes: > I suggest that everyone who feels that linuxpeople is stupid should > ignore him NOW. Everyone who thinks there is any hope he will get his > system up should support him by private mail NOW. While in general I agree with the sentiment of your message, I intend to keep helping people with qmail installation problems on the qmail mailing list, as I think that's what it's for. If Dan disagrees with me, it's his list and he can tell me to stop, but other people not liking to deal with people with a very beginning knowledge of Linux isn't sufficient reason for me to stop helping them. The first time I installed Red Hat, I too found it extremely unintuitive that the package named glibc-devel is *not* for developing glibc, like it sounds, but is instead needed if you intend to compile anything at all ever. I've since then gotten used to the -devel naming convention, but I still find it somewhat odd and I'm happy to help someone else out who had the same misunderstanding that I had and did the same thing that I did the first time I installed Red Hat (namely not install that package and then wonder where all my include files went). -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
On Wed, Sep 13, 2000 at 03:22:17PM -0400, Peter Green wrote: [...] >>> Finally, if you *still* had questions on the RPM install (sorry I'm harping >>> on it, but I've used it extensively, >> what the rpm? > Yes, Bruce Guenter's qmail+patches RPM. Note that the qmail RPM's that are linked to at the top of <URL:http://www.qmail.org/top.html> are in fact the "Memphis" RPMs. Vince.
I'm a bit new to qmail, but his instructions seem to have missed a few points, such as creating a /var/qmail directory, or even creating the nofiles group. He seems, to me anyway, to have missed a few lines when pasting in from the INSTALL.ids Dave On Wed, 13 Sep 2000, It appears Frank Tegtmeyer said....... > > > http://www.securityfocus.com/focus/linux/articles/qmail.html > > Replacing your MTA with qmail > > Hm. It's neither a review nor is the title correct. > It's only an excerpt from BLURB and INSTALL as far as I can see. > > It's good to have qmail mentioned on securityfocus but this article could > provide much more than it actually does. > > Regards, Frank >
Sorry, this is probably a stupid question but I am trying to sort out selective relaying. I'm trying to add the line: -x /etc/tcp.smtp.cdb into my system boot scripts after tcpserver, but I can't find which script this is ment to go into. I'm using Redhat 6.2 i386. Any help would be nice, thanks! Jon. -- ICMP - The protocol that likes to go: PING!
it should go into the script which starts qmail-smtpd for me that is /var/qmail/supervise/qmail-smtpd/run ----- Original Message ----- From: "Jonathan Fanti" <[EMAIL PROTECTED]> To: "Qmail List" <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 6:16 AM Subject: TCP server > Sorry, this is probably a stupid question but I am trying to sort out > selective relaying. I'm trying to add the line: -x /etc/tcp.smtp.cdb > into my system boot scripts after tcpserver, but I can't find which > script this is ment to go into. I'm using Redhat 6.2 i386. > > Any help would be nice, thanks! > > Jon. > -- > ICMP - The protocol that likes to go: PING!
I didn't see a response to this so I thought I would try again . . Thanks, Phil. >Date: Thu, 07 Sep 2000 23:43:10 +0100 >To: [EMAIL PROTECTED] >From: Phil Rhoades <[EMAIL PROTECTED]> >Subject: mail works kmail/NS messenger don't on private WAN > >I have a private WAN set up - two Linux servers with a router etc in between: > > 192.16.0.100 nsw.chu.com.au > >and > > 192.16.8.25 bcb.chu.com.au > >- I can use "mail" to send mail from nsw to bcb no problem (therefore >rcpthosts and smtproutes should be OK) but Kmail and Netscape Messenger >fail with a message like: > > Sending failed > A SMTP error occurred > Command: RCPT > Response: 553 sorry, that domain isn't in my list of allowed > rcpthosts (#5.7.1) > Return code: 533 > >I have tried putting both server details in rcpthosts and also the >wildcard domain (.chu.com.au) but still no luck . . > >Any suggestions? > >Thanks, > >Phil. - Philip Rhoades Pricom Pty Limited (ACN 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:0411-185-652 Fax: +61:2:8923-5363 E-mail: [EMAIL PROTECTED]
On Wed, 13 Sep 2000, Phil Rhoades wrote: > I didn't see a response to this so I thought I would try again . . You need to enable selective relaying: http://Web.InfoAve.Net/~dsill/lwq.html#relaying Vince. > > Thanks, > > Phil. > > >Date: Thu, 07 Sep 2000 23:43:10 +0100 > >To: [EMAIL PROTECTED] > >From: Phil Rhoades <[EMAIL PROTECTED]> > >Subject: mail works kmail/NS messenger don't on private WAN > > > >I have a private WAN set up - two Linux servers with a router etc in between: > > > > 192.16.0.100 nsw.chu.com.au > > > >and > > > > 192.16.8.25 bcb.chu.com.au > > > >- I can use "mail" to send mail from nsw to bcb no problem (therefore > >rcpthosts and smtproutes should be OK) but Kmail and Netscape Messenger > >fail with a message like: > > > > Sending failed > > A SMTP error occurred > > Command: RCPT > > Response: 553 sorry, that domain isn't in my list of allowed > > rcpthosts (#5.7.1) > > Return code: 533 > > > >I have tried putting both server details in rcpthosts and also the > >wildcard domain (.chu.com.au) but still no luck . . > > > >Any suggestions? > > > >Thanks, > > > >Phil. > > - > Philip Rhoades > > Pricom Pty Limited (ACN 003 252 275) > GPO Box 3411 > Sydney NSW 2001 > Australia > Mobile: +61:0411-185-652 > Fax: +61:2:8923-5363 > E-mail: [EMAIL PROTECTED] > > -- ========================================================================== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
At 07:37 13/09/2000 -0400, you wrote: >On Wed, 13 Sep 2000, Phil Rhoades wrote: > > > I didn't see a response to this so I thought I would try again . . > >You need to enable selective relaying: > > http://Web.InfoAve.Net/~dsill/lwq.html#relaying > >Vince. Tried that . . no luck . . At 13:41 13/09/2000 +0200, Frank Tegtmeyer wrote: > > >- I can use "mail" to send mail from nsw to bcb no problem (therefore > > >rcpthosts and smtproutes should be OK) but Kmail and Netscape Messenger > > >fail > >If you include both destinations in rcpthosts it should work. >Please provide rcpthosts, locals and smtproutes for both systems. > >Regards, Frank Local Workstation: - IP: 192.168.0.108 + kmail Local Server: - IP: 192.168.0.100 - locals: nsw.chu.com.au - rcpthosts: nsw.chu.com.au & bcb.chu.com.au (on separate lines of course) - smtproutes: bcb.chu.com.au:192.168.8.25 Remote Workstation: - IP: 192.168.8.21 + MS OE Remote Server: - IP: 192.168.8.25 - locals: bcb.chu.com.au - rcpthosts: bcb.chu.com.au - smtproutes: nsw.chu.com.au:192.168.0.100 - Mail sent (using mail) from the remote server to me on the local server ([EMAIL PROTECTED]) can be retrieved by the local workstation. - Mail sent from the local workstation addressed to the me on the remote server ([EMAIL PROTECTED]) gives the message: Sending failed A SMTP error occurred Command: RCPT Response: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) Return code: 533 - Mail sent from the remote workstation addressed to the me on the local server gives a similar message: Thanks, Phil. - Philip Rhoades Pricom Pty Limited (ACN 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:0411-185-652 Fax: +61:2:8923-5363 E-mail: [EMAIL PROTECTED]
With selective relaying properly set up, the contents of rcpthosts is ignored. Post the contents of tcp.smtp, your qmail-smtpd startup line and how you built tcp.smtp.cdb. Alternately you might try putting .chu.com.au in your rcpthosts on the remote system on a line all by itself. Vince. On Thu, 14 Sep 2000, Phil Rhoades wrote: > At 07:37 13/09/2000 -0400, you wrote: > >On Wed, 13 Sep 2000, Phil Rhoades wrote: > > > > > I didn't see a response to this so I thought I would try again . . > > > >You need to enable selective relaying: > > > > http://Web.InfoAve.Net/~dsill/lwq.html#relaying > > > >Vince. > > Tried that . . no luck . . > > At 13:41 13/09/2000 +0200, Frank Tegtmeyer wrote: > > > >- I can use "mail" to send mail from nsw to bcb no problem (therefore > > > >rcpthosts and smtproutes should be OK) but Kmail and Netscape Messenger > > > >fail > > > >If you include both destinations in rcpthosts it should work. > >Please provide rcpthosts, locals and smtproutes for both systems. > > > >Regards, Frank > > Local Workstation: > - IP: 192.168.0.108 + kmail > > Local Server: > - IP: 192.168.0.100 > - locals: nsw.chu.com.au > - rcpthosts: nsw.chu.com.au & bcb.chu.com.au (on separate lines of course) > - smtproutes: bcb.chu.com.au:192.168.8.25 > > Remote Workstation: > - IP: 192.168.8.21 + MS OE > > Remote Server: > - IP: 192.168.8.25 > - locals: bcb.chu.com.au > - rcpthosts: bcb.chu.com.au > - smtproutes: nsw.chu.com.au:192.168.0.100 > > - Mail sent (using mail) from the remote server to me on the local server > ([EMAIL PROTECTED]) can be retrieved by the local workstation. > - Mail sent from the local workstation addressed to the me on the remote > server ([EMAIL PROTECTED]) gives the message: > > Sending failed > A SMTP error occurred > Command: RCPT > Response: 553 sorry, that domain isn't in my list of allowed > rcpthosts (#5.7.1) > Return code: 533 > > - Mail sent from the remote workstation addressed to the me on the local > server gives a similar message: > > Thanks, > > Phil. > - > Philip Rhoades > > Pricom Pty Limited (ACN 003 252 275) > GPO Box 3411 > Sydney NSW 2001 > Australia > Mobile: +61:0411-185-652 > Fax: +61:2:8923-5363 > E-mail: [EMAIL PROTECTED] > > -- ========================================================================== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
> >- I can use "mail" to send mail from nsw to bcb no problem (therefore > >rcpthosts and smtproutes should be OK) but Kmail and Netscape Messenger > >fail If you include both destinations in rcpthosts it should work. Please provide rcpthosts, locals and smtproutes for both systems. Regards, Frank
Hi all, Thanks for your responses. I still don't know how duplication actually occurs ;( but the problem went away :) . I RTFM a littly more thoroughly - qmail-inject (I'm sorry I didn't do that more earlier.) man qmail-inject, quoted, about the 6th line from the top: "DESCRIPTION qmail-inject reads a mail message from its standard input..." duh! (*blush*blush*cough*cough*) So instead of my old line in that perl script: $sendmail = '/usr/sbin/sendmail -t'; I rewrote that to point to qmail-inject: $sendmail = '/var/qmail/bin/qmail-inject'; and yes! No more dups. Now I could create about 10000 trash accounts and do my ball-park figure stress test :). Hope this resolves someone elses PERL/duplicate agenda. Thanks again, jamie - inching my way up the qmail mountain :) ps the way qmail does things (and of course the various packages related to qmail which I came across) is indeed very interesting. #---------#---------#---------#---------#---------#---------#---------# -- If somebody can help create a search engine for my room, I will call them a Saint... GUI == Graphical User Interf e r e n c e --- wahhhhhhhh!
I've setup qmail with yet another virtual domain with .qmail-domain-default and everything is fine. Now for this domain I'd like to bounce back non-user addresses, I removed the default file and this works okay. My problem is that the bounce message uses the 'MAILER_DAEMON@localnet' address and not the virtual 'MAILER_DAEMON@domain' as I would like. Can anyone help me with this problem? I think people would get a little confused if the bounce mail seems to come from a different domain. Also is it possible to put a translation under the english message? Thanks, Magnus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13 Sep 2000, at 14:35, Magnus 0 wrote: > I've setup qmail with yet another virtual domain with > .qmail-domain-default and everything is fine. > > Now for this domain I'd like to bounce back non-user addresses, I > removed the default file and this works okay. My problem is that the > bounce message uses the 'MAILER_DAEMON@localnet' address and not the > virtual 'MAILER_DAEMON@domain' as I would like. Can anyone help me > with this problem? You may change control/bouncefrom and control/bouncehost. However, the setting is global. You may create and inject the bounce message yourself and return 99 from your .qmail-default. > I think people would get a little confused if the bounce mail seems to > come from a different domain. I wouldn't think so. When you get a normal letter back as "undeliverable - no such address", do you care who returned it? > Also is it possible to put a translation under the english message? You must edit the sources. You may, easily, but don't break QSBMF (qmail simple bounce message format). -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 -- QDPGP 2.61b Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOb9oklMwP8g7qbw/EQJdEQCdE7QWP+1x6CKPBhGxvcrlCEG4TmEAni0i yd+Rsn2Usl08Se14BNQYwVBz =jOaT -----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]
On Wed, Sep 13, 2000 at 02:44:17PM +0200, Petr Novotny wrote: > On 13 Sep 2000, at 14:35, Magnus 0 wrote: > > I've setup qmail with yet another virtual domain with > > .qmail-domain-default and everything is fine. > > Now for this domain I'd like to bounce back non-user addresses, I > > removed the default file and this works okay. My problem is that the > > bounce message uses the 'MAILER_DAEMON@localnet' address and not the > > virtual 'MAILER_DAEMON@domain' as I would like. Can anyone help me > > with this problem? > You may change control/bouncefrom and control/bouncehost. > However, the setting is global. > You may create and inject the bounce message yourself and return > 99 from your .qmail-default. Or you can patch the bouncesaying program to use the environment variable $HOST that qmail-local sets. Then put |bouncesaying "Denna mailadress finns inte" or whatever language error message you want into the default qmail file of every domain. > > I think people would get a little confused if the bounce mail seems to > > come from a different domain. > I wouldn't think so. When you get a normal letter back as > "undeliverable - no such address", do you care who returned it? I agree. > > Also is it possible to put a translation under the english message? > You must edit the sources. You may, easily, but don't break > QSBMF (qmail simple bounce message format). See above. -Johan -- Johan Almqvist
On Tue, Sep 12, 2000 at 04:32:52PM -0400, Michael T. Babcock wrote: > For the sake of answering the original questionner w.r.t. reasoning, from > RFC974 (which is standard 0014): > > Note that the algorithm to delete irrelevant RRs breaks if LOCAL has > a alias and the alias is listed in the MX records for REMOTE. (E.g. > REMOTE has an MX of ALIAS, where ALIAS has a CNAME of LOCAL). This > can be avoided if aliases are never used in the data section of MX > RRs. > > cf. http://www.faqs.org/rfcs/rfc974.html > > This is the only mention of the non-use of CNAMEs in the mail standards. Mail standards aren't the only standards. The origin of all this fuss is probably RFC1034 (also part of STD 13): 3.6.2. Aliases and canonical names ... CNAME RRs cause special action in DNS software. When a name server fails to find a desired RR in the resource set associated with the domain name, it checks to see if the resource set consists of a CNAME record with a matching class. If so, the name server includes the CNAME record in the response and restarts the query at the domain name specified in the data field of the CNAME record. The one exception to this rule is that queries which match the CNAME type are not restarted. For example, suppose a name server was processing a query with for USC- ISIC.ARPA, asking for type A information, and had the following resource records: USC-ISIC.ARPA IN CNAME C.ISI.EDU C.ISI.EDU IN A 10.0.0.52 Both of these RRs would be returned in the response to the type A query, while a type CNAME or * query should return just the CNAME. Domain names in RRs which point at another name should always point at the primary name and not the alias. This avoids extra indirections in accessing information. For example, the address to name RR for the above host should be: 52.0.0.10.IN-ADDR.ARPA IN PTR C.ISI.EDU rather than pointing at USC-ISIC.ARPA. Of course, by the robustness principle, domain software should not fail when presented with CNAME chains or loops; CNAME chains should be followed and CNAME loops signalled as an error. Jost -- | [EMAIL PROTECTED] Please help stamp out spam! | | Postmaster, JAPH, resident answer machine am RZ der RUB | | Pluralitas non est ponenda sine necessitate | | William of Ockham (1285-1347/49) |
----- Original Message ----- From: "Petr Novotny" <[EMAIL PROTECTED]> > On 12 Sep 2000, at 16:32, Michael T. Babcock wrote: > > > cf. http://www.faqs.org/rfcs/rfc974.html > > > > This is the only mention of the non-use of CNAMEs in the mail > > standards. > > I beg to differ. Please have a look at RFC1912, called "Common > DNS errors". Quoting section 2.4: > > [RFC 1034] in section 3.6.2 says this should not be done, and [RFC > > 974] explicitly states that MX records shall not point to an alias > > defined by a CNAME. This results in unnecessary indirection in > > accessing the data, and DNS resolvers and servers need to work more > > to get the answer. If you really want to do this, you can > > accomplish the same thing by using a preprocessor such as m4 on > > your host files. RFC1912 is "Category: Informational" and is a recommendation, not an Internet standard (that was my original point). RFC 1034 is also a non-standard recommendation (only) from 1987 and I'm unable to open RFC 974 for perusal right now. Please note the difference ... RFCs are good reading. HTTP and several other non-standard protocols are entirely implemented based on RFCs, but are allowed to diverge from those RFCs without anyone having the right to be terribly upset because they are /not/ Internet standards. It is sometimes a good idea to follow the recommendations in non-standards RFCs. In many cases, citing 'its in an RFC' is irrelevant though, as the carrier pigeon implementation of IP should demonstrate.
Fadli Syarid wrote: > > hi all > can i use my domain as my adress > eg.. > my host: omni.arc.itb.ac.id > i want my adress like this [EMAIL PROTECTED] > what should i do..? At first: It seems to me as if you are running a qmail server on your machine with the address omni.arc.itb.ac.id and now you want it to process all the mail for arc.itb.ac.id If this is what you want, you have to do two things: 1) You have to make sure, that all messages, that you send out seem to come from arc.itb.ac.id and not from omni.arc.itb.ac.id by default. you do this by editing /var/qmail/control/defaulthost or /var/qmail/control/defaultdomain. These files contains the default domain suffix. I do not really know the difference in the meaning of these two files, but it should be enough to edit one. Perhaps someone knows the difference and can tell me. Do: echo arc.itb.ac.id > /var/qmail/control/defaulthost >From now on, all mailaddresses that have no hostpart are going to [EMAIL PROTECTED] 2) But more important is to tell the world, that omni.arc.itb.ac.id is the default mailserver for your domain arc.itb.ac.id. To do this you have to configure the DNS server of your domain properly. you need an MX (mail exchanger) entry, that points to your mailservers. something like this in your named configuration files should do it: arc.itb.ac.id IN MX 10 omni.arc.itb.ac.id If you are using an other nameserver, you have to consult its documentation. If this is not done, MTAs around the world would not know, how to find the host, that processes the mail for arc.itb.ac.id. I hope this helped you. > > i am sorry if my english bad cause english not my native..:) I dont think mine is better ;) Greetings, Melanie
On Wed, Sep 13, 2000 at 03:19:06PM +0200, Melanie Desaive wrote: [snip] > you do this by editing /var/qmail/control/defaulthost or > /var/qmail/control/defaultdomain. These files > contains the default domain suffix. I do not really know > the difference in the meaning of these two files, but it should be > enough to edit one. Perhaps someone knows the difference and can > tell me. man 8 qmail-inject. But, the short version, defaultdomain gets appended to an address with a dotless hostname, and defaulthost gets appended to a hostless address. RC -- +------------------- | Ricardo Cerqueira | PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42 | Novis - Engenharia ISP / Rede T�cnica | P�. Duque Saldanha, 1, 7� E / 1050-094 Lisboa / Portugal | Tel: +351 21 0100000 - Fax: +351 21 0100001
PGP signature
On Tue, Sep 12, 2000 at 09:27:40PM -0600, James Shelby wrote: > Thanks Dale, still no luck...same error message. Here is a little more > information that might tell someone that I have it configured wrong... First, did you try changing your inetd.conf file as in my previous post? Did you HUP inetd? > Say I have a user called johnd in /home/johnd I have a Mail and Maildir > directories along with a Mailbox file. In /var/spool/mail I have a johnd > link that goes to the /home/johnd/Mailbox Does johnd have a .qmail file? If so, what's in it? If not, what's the default delivery in /var/qmail/rc? If your default delivery is ./Maildir/, then the Mail directory, Mailbox file, and symlinks in /var/spool/mail are unnecessary, but shouldn't cause any problems. Chris
"James Shelby" <[EMAIL PROTECTED]> wrote: >So far qmail has been easy to install with the exception of the pop service. >I have the 110 port open and it does function however it states this user >has no $HOME/Maildir when in fact the Maildir does exist in the /home/user >directory. Is it really a maildir? Did you create it using maildirmake? Is it owned by the user? Tip o' the day: check out "Life with qmail", http://lwq.w3.to/ -Dave
Anyone have any idea where the qmail-cyrus link went to? The link is broken in LWQ.=G=
-- |-----------------------Quote of the Moment-------------------------|When properly administered, vacations do not diminish productivity: for every week you're away and get nothing done, there's another when your boss is away and you get twice as much done. -- Daniel B. Luten
"Robin S. Socha" wrote: > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 04:32]: > > Hello I have documented each step up until they fail. > > Damn, you are *STUPID*. When someone tells you to post a *SHORT* and > *PREGNANT* error message, why do you send > 600 lines? And HOT damn, you are rude! Got too much free time on your hands? Nice to see you are leading by example. People can do silly things, that doesn't mean you need mow them down. No class. -Stephen-
----- Original Message ----- From: "Michael T. Babcock" <[EMAIL PROTECTED]> To: "Robin S. Socha" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 8:15 AM Subject: Re: Linuxluser thread (Was: linuxpeople thread) > Because every other time someone posts an error message, they get told to > send ALL their logs. So now, someone does, and they're told they're an > idiot for not reading your mind? Amen brother! > > ----- Original Message ----- > From: "Robin S. Socha" <[EMAIL PROTECTED]> > > > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 04:32]: > > > Hello I have documented each step up until they fail. > > > > Damn, you are *STUPID*. When someone tells you to post a *SHORT* and > > *PREGNANT* error message, why do you send > 600 lines? > >
* Michael T. Babcock <[EMAIL PROTECTED]> [000913 11:13]: > "Robin S. Socha" <[EMAIL PROTECTED]> > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 04:32]: [quoting readjusted] > > > I have documented each step up until they fail. > > Damn, you are *STUPID*. When someone tells you to post a *SHORT* and > > *PREGNANT* error message, why do you send > 600 lines? > Because every other time someone posts an error message, they get told > to send ALL their logs. So now, someone does, and they're told > they're an idiot for not reading your mind? |[root@www local]# cd /usr/local/qmail-1.03/ |[root@www qmail-1.03]#ls [~500 lines nuked] You call that a log? Why don't you learn to use your MUA in a decent way instead of lamenting the fate of an unknown luser. Your pathetic whining sucks. -- Down, not across
Because every other time someone posts an error message, they get told to send ALL their logs. So now, someone does, and they're told they're an idiot for not reading your mind? ----- Original Message ----- From: "Robin S. Socha" <[EMAIL PROTECTED]> > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 04:32]: > > Hello I have documented each step up until they fail. > > Damn, you are *STUPID*. When someone tells you to post a *SHORT* and > *PREGNANT* error message, why do you send > 600 lines?
On Wed, Sep 13, 2000 at 11:15:43AM -0400, Michael T. Babcock wrote: > Because every other time someone posts an error message, they get told to > send ALL their logs. So now, someone does, and they're told they're an > idiot for not reading your mind? This is boring, but to be correct, mostly people want the logs/details put up on a web site and have the URL posted to the list. Regards. > > ----- Original Message ----- > From: "Robin S. Socha" <[EMAIL PROTECTED]> > > > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 04:32]: > > > Hello I have documented each step up until they fail. > > > > Damn, you are *STUPID*. When someone tells you to post a *SHORT* and > > *PREGNANT* error message, why do you send > 600 lines? >
How do you manage to get back to MUAs in most messages you write? How exactly am I mis-using my MUA? Hmmm? I'm not misusing my MUA. I didn't complain about how messages looked, yours, mine or others'. You're the one who's been whining. That can be verified by the archives if you have some problem with your memory. You whine CONSTANTLY about peoples' MUAs. Don't tell us to change, follow your own advice and shut-up. ----- Original Message ----- From: "Robin S. Socha" <[EMAIL PROTECTED]> > You call that a log? Why don't you learn to use your MUA in a decent way > instead of lamenting the fate of an unknown luser. Your pathetic whining > sucks.
"Robin S. Socha" wrote: > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000913 04:32]: > > Hello I have documented each step up until they fail. > > Damn, you are *STUPID*. When someone tells you to post a *SHORT* and > *PREGNANT* error message, why do you send > 600 lines? > > > /compile qmail-local.c > > qmail-local.c:1: sys/types.h: No such file or directory > > make: *** [qmail-local.o] Error 1 > > /usr/src/linux/include/linux/types.h > > Which part of "did you install your kernel sources" from, like, a day > ago, do I have to read out s-l-o-w-l-y to you again? > http://www.ornl.gov/its/archives/mailing-lists/qmail/2000/09/msg00774.html "Dave, I really think you ought to sit down, take a stress pill, and think this over." -- HAL9K Eric
On Wed, 13 Sep 2000, Petr Novotny wrote: 1. What's that? qmail's queue can be mounted noatime? Huh! Please try "grep atime /usr/src/qmail/qmail-1.03/*c" and then withdraw your claims. atime is used to identify ossified files in the queue. If you look closely at the source you'll see that ossified files are still detected with noatime turned on. The atime value is set to the creation time in this case. The only undesired effect of using noatime is that a file may be falsely identified as ossified in the rare case that reception of the file takes longer than 36 hours. Same goes for files in a maildir's tmp directory. The performance win from noatime can be significant. I have run a large service for many years (since qmail-0.72) with the queue and message store mounted noatime with no harmful effects. -- Jeff Hayward
> - Mail sent from the local workstation addressed to the me on the remote > server ([EMAIL PROTECTED]) gives the message: Hm. Your setup should work. The only problems I can think of now are: - Your qmail-smtpd does not pick the "right" rcpthosts. You may check if you can send mail through SMTP to the local server (nsw). If that fails, something with your qmail-smtpd is wrong. - Your rcpthosts file contains strange (invisible?) characters. Try to add a line which contains .chu.com.au only (like Vince suggested). This must work then. Regards, Frank.
> Are you really sure you want the misery of running a mail server on a > 486 with only 8 Mb of RAM? 8 Megs of ram is kind of minimal and downright stingy when it comes down to it considering how cheap ram is, particularly for operating a linux kernel. Not many user programs can run at the same time. According to my pair of qmail servers, which are admitedly a couple powerful HP LPR systems with gobs of RAM, qmail uses about 400K of system memory for each program, and not enough CPU to note. (TOP column display customized and irrelevant programs axed in the below copy) PID TSIZE DSIZE SIZE TRS RSS SHARE LIB %CPU %MEM COMMAND 1080 30 3968M 488 36 488 316 0 0.0 0.1 qmail-send 17354 17 3968M 456 24 456 380 0 0.0 0.1 qmail-remote 1081 3 3968M 428 8 428 348 0 0.0 0.1 splogger 1083 8 3968M 376 16 376 288 0 0.0 0.1 qmail-rspawn 1084 5 3968M 352 12 352 284 0 0.0 0.1 qmail-clean 1082 11 3968M 348 20 348 276 0 0.0 0.1 qmail-lspawn 1085 30 3968M 336 36 336 272 0 0.0 0.1 tcpserver Given that it uses so little space, I think that assuming there is swap space defined and you're running a minimal kernel, you could probably run 10 to 20 remote/local delivery sessions. Sure, it may not blast mail out like a high end mailing list server, but it'll be more functional than, say, SENDMAIL. ;P The limit is probably more memory vs. swap speed rather than CPU power. David
On Wed, Sep 13, 2000 at 08:56:39AM -0700, Ihnen, David wrote: > > Are you really sure you want the misery of running a mail server on a > > 486 with only 8 Mb of RAM? > > 8 Megs of ram is kind of minimal and downright stingy when it comes down to > it considering how cheap ram is, particularly for operating a linux kernel. > Not many user programs can run at the same time. But as you say... > Given that it uses so little space, I think that assuming there is swap > space defined and you're running a minimal kernel, you could probably run 10 > to 20 remote/local delivery sessions. Sure, it may not blast mail out like Let's say it can handle just one delivery every 6 seconds*. That amounts to 8000+ deliveries per day. Vastly more than most small offices need to do. The only misery might be if he has people popping off of this box, even then, most clients do this as a background activity so any delays are not really noticeable. And, if it's a firewall mail system only, it will amlost certainly be adequate for, say, 20 average users. (8000/20 = 400 messages per day). In other words, if the box is reliable and available and his load is less than that, then no problems. Regards. * And that's assuming it consumes all the resources of that system during that delivery, in practise a single delivery is mostly latency bound so my estimates of load are excessively conservative.
Ihnen, David <[EMAIL PROTECTED]> writes on 13 September 2000 at 08:56:39 -0700 > > Are you really sure you want the misery of running a mail server on a > > 486 with only 8 Mb of RAM? > > Given that it uses so little space, I think that assuming there is swap > space defined and you're running a minimal kernel, you could probably run 10 > to 20 remote/local delivery sessions. Sure, it may not blast mail out like > a high end mailing list server, but it'll be more functional than, say, > SENDMAIL. ;P The limit is probably more memory vs. swap speed rather than > CPU power. That's in the ballpark with what I ran successfully on my 386/25 with 8Mb, so it's probably good advice. -- Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
"Ihnen, David" wrote: > > 8 Megs of ram is kind of minimal and downright stingy when it comes down to > it considering how cheap ram is, particularly for operating a linux kernel. > Not many user programs can run at the same time. <SNIP> > Given that it uses so little space, I think that assuming there is swap > space defined and you're running a minimal kernel, you could probably run 10 > to 20 remote/local delivery sessions. Sure, it may not blast mail out like > a high end mailing list server, but it'll be more functional than, say, > SENDMAIL. ;P The limit is probably more memory vs. swap speed rather than > CPU power. I'm not denying that the machine is up to it, I just think that *configuring* a machine like that is absolute murder, having tried it myself. Compiles take a couple of eternities, opening files in editors is slow... it's just general hell. It's not hard to find an old Pentium that would be easier to set up to handle mail... =) -Stephen-
> -----Original Message----- > From: Stephen F. Bosch [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 13, 2000 11:01 AM > To: [EMAIL PROTECTED] > Subject: Re: qmail on little machines? (was part of linuxuser thread) > > > I'm not denying that the machine is up to it, I just think that > *configuring* a machine like that is absolute murder, having tried it > myself. Compiles take a couple of eternities, opening files in editors > is slow... it's just general hell. > > It's not hard to find an old Pentium that would be easier to set up to > handle mail... =) You're not paid by the hour, are you... ;) David
"Stephen F. Bosch" wrote: > > to 20 remote/local delivery sessions. Sure, it may not blast mail out like > > a high end mailing list server, but it'll be more functional than, say, > > SENDMAIL. ;P The limit is probably more memory vs. swap speed rather than > > CPU power. > > I'm not denying that the machine is up to it, I just think that > *configuring* a machine like that is absolute murder, having tried it > myself. Compiles take a couple of eternities, opening files in editors > is slow... it's just general hell. > > It's not hard to find an old Pentium that would be easier to set up to > handle mail... =) > > -Stephen- I adgree. You could easily run qmail on a small machine (486/66 with 8 megs) to do 10,000 to 30,000 messages a day which will be fine for less then 100 users. If you keep the config file simple and you compiles on a fast machine, you should haven't any problems, and you won't lose your mind. In most cases, once qmail is setup and doing what you need it to do, it's quite normal to only add new users and edit .qmail files which can be done with echo and a user add script. Logging is another story. When you go to load that 1 meg log file into vi, it may take a while, but if you do reading and storeage of logs on, this too can be advoided. So, the only real limiting factor of this small machine is the 8 megs and that mainly for things other then qmail. I would at least put 32 megs in the machine just to keep things easy on the machine. -Steven Rice
Thus spake Steven Rice ([EMAIL PROTECTED]): > I adgree. You could easily run qmail on a small machine (486/66 with 8 > megs) to do 10,000 to 30,000 messages a day which will be fine for less > then 100 users. d'accord. I use to be the maintainer of different mailinglists with a overall load of ~200 incoming and ~140000 outgoing messages per day. For more than one year the whole thing ran on 386SX 25 with 8MB RAM. Boy, that machine _was_ under load, but worked -- until memory failures ruined the uptime too frequently and more power for http was requested. cheers, oec
> > It's not hard to find an old Pentium that would be easier to set up to > > handle mail... =) Not only that, it's not hard to find someone with an unused machine with 32 megs or so in 72-pin SIMMS, so you could put a more reasonable amount of RAM into the mail server.... steve
"Ihnen, David" wrote: > > > -----Original Message----- > > From: Stephen F. Bosch [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, September 13, 2000 11:01 AM > > To: [EMAIL PROTECTED] > > Subject: Re: qmail on little machines? (was part of linuxuser thread) > > > > > > I'm not denying that the machine is up to it, I just think that > > *configuring* a machine like that is absolute murder, having tried it > > myself. Compiles take a couple of eternities, opening files in editors > > is slow... it's just general hell. > > > > It's not hard to find an old Pentium that would be easier to set up to > > handle mail... =) > > You're not paid by the hour, are you... ;) Oh, I am -- but I still have a few scruples left =) (I also like my brain cells alive and my eyes working ;) ) -Stephen-
Hello, I am underway installing a new box with qmail, this time using the new daemontools-0.70 plus ucspi-tcp-0.88 and it generally works like a champ. Although I'm not yet convinced that the two-stage pipe thing is a sufficient replacement for full pipe control in supervise, this is far easier to get right than the earlier method was. Now the problem: I started a pop session, with my maildir emtpy: telnet host 110, user xyz, pass abc list -> 0 Then I sent me a message which got placed in my Maildir/new... list-> 0 _still_ I waited several seconds and tried again, and it was still 0... When I finished the pop3 session and started a new one, I had no problem seeing and reading the message. This is under Linux, 2.2.17-pre (Debian 2.2 default kernel). Am I bitten by Linux metadata semantics? Does qmail-pop3d scan the mailbox only on login or at (long) fixed intervals? Best Regards, --Toni++
On Wed, Sep 13, 2000 at 06:17:49PM +0200, Toni Mueller wrote: > Now the problem: > > I started a pop session, with my maildir emtpy: > telnet host 110, user xyz, pass abc > list -> 0 > Then I sent me a message which got placed in my > Maildir/new... > > list-> 0 _still_ > > I waited several seconds and tried again, and it was > still 0... When I finished the pop3 session and started > a new one, I had no problem seeing and reading the > message. > > This is under Linux, 2.2.17-pre (Debian 2.2 default > kernel). > > Am I bitten by Linux metadata semantics? Does qmail-pop3d > scan the mailbox only on login or at (long) fixed intervals? Nope you're being bitten by the way the pop daemon works. It only scans for mail on startup, not every time you issue a command to it. That's normal behaviour for the majority of pop servers (I can't speak for them all of course). Clients re-connect rather than stay connected so it's not a real-world problem. Regards.
Hello, On Wed, Aug 16, 2000 at 10:28:48AM -0500, Mate Wierdl wrote: > On Wed, Aug 16, 2000 at 09:55:53AM -0500, Ben Beuchler wrote: > > On Wed, Aug 16, 2000 at 07:08:28AM -0500, Mate Wierdl wrote: > > > but would not it be relatively simple to implement a server software > > > using tcpserver that would just lookup an IP number in a .cdb database > > > of IP numbers, and send an appropriate response? A client might be hmm. I don't understand the question. For ucspi-tcp-0.88, I get from http://cr.yp.to/ucspi-tcp/rblsmtpd.html (slightly wrapped): ----------------- cut Options: -r base: Use base as an RBL source. An IP address a.b.c.d is listed by that source if d.c.b.a.base has a TXT record. rblsmtpd uses the contents of the TXT record as an error message for the client. ----------------- cut and: ----------------- cut You may supply any number of -r and -a options. rblsmtpd tries each source in turn until it finds one that lists or anti-lists $TCPREMOTEIP. It also tries an RBL source of rbl.maps.vix.com if you do not supply any -r options. See http://maps.vix.com/rbl/ for more information about rbl.maps.vix.com. If you want to run your own RBL source or anti-RBL source for rblsmtpd, you can use rbldns from the djbdns package. ----------------- cut I didn't try this, but imho this clearly says "-r maps.vix.com gets you the default behaviour of asking Paul Vixie". So, what's the problem? You need to axfr the zone from somewhere and massage that into a cdb the rbldns would probably use. That could be done with a cron job. How much mail you then deny is up to you... But that's one thing every sysadmin has to decide for oneself, do I have a default closed (-c) or open (-C) setup when my rbl servers fail? Best Regards, --Toni++
[EMAIL PROTECTED] wrote: >I do know IMAP is a protocol.What I said is IMAP4,a software package developed by UW. >It can also act as a MTA,right? No. -Dave
----- Original Message ----- From: "Petr Novotny" <[EMAIL PROTECTED]> > On 12 Sep 2000, at 16:06, Michael T. Babcock wrote: > > > How does a different filesystem, like ReiserFS help? Hypothetically? > > Any system which doesn't scan directories in linear order but using > binary search (keeping directory entries sorted, or indexed) helps a > lot. Not only ReiserFS, but also NTFS lie in that domain. (Well, I > *think* ReiserFS lies in that domain; I *know* NTFS does.) > [ ... ] > Hell, I would like to see ext2 with much better scaling - Maildirs > would finally stop to suck when overcrowded. But *personally* I > trust more the code from the "mainstream distribution" (read: ext2) > then patching my kernel (read: reiserFS). I'll wait until a better > filesystem claws its way into RedHat distro. :-) I'm running ReiserFS on our non-critical partition (squid caching) and have been for about 6 months solid. The only errors or glitches I've come across is running out of space incorrectly (df -h reports one amount, but the filesystem reports an error when creating a file). This would be an issue -- but in this case, I'm running things close to the line (I've told Squid to use 450M of a 500M partition). There is a project to modify qmail 1.03 to work more efficiently with ReiserFS' design; see their mailing list archives if you want details.
Michael T. Babcock <[EMAIL PROTECTED]> writes on 12 September 2000 at 16:06:16 -0400 > How does a different filesystem, like ReiserFS help? Hypothetically? By reducing disk bandwidth used on the queue disk(s). This is often the limiting factor on a high-volume mail server running qmail. There are a lot of fsyncs done, to make sure the mail is securely on the disk before formally accepting it (returning success from smtpd or inject). -- Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
>It takes approximately 6 hours for the script to complete, each >message invokes a separate qmail-inject process as the mails are >customised with the persons name / details etc. The concurrency only >seems to hit about 30- 40 while the script is still pumping messages >into qmail-inject. I would definitely call qmail-remote directly, then fall back to qmail-queue if the qmail-remote fails. Since you know that each message has a single recipient and you can assume that all the recipients are remote, you can skip all of the overhead of queueing and dequeueing all message that get delivered on the first try. (Even if a few of them are local, they'll still get delivered by looping back to the local SMTP daemon.) The interface to qmail-remote is pretty simple; I've driven it from a 68 line perl script, although it'd take a few extra lines to manage a pool of qmail-remotes to keep up the concurrency you'd want for an application like this. I believe that Russ Nelson has done this sort of thing in the past with great success. -- 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
Hi all, I've got a couple of places that like to subscribe non-existant email addresses to mailing lists without confirmation. One of these bastards is winvite.com. The problem I'm having is that they don't send their emails with a "From" header, so control/badmailfrom with an @winvite.com entry is not blocking their mail. The other problem is I can't block them by IP because they seem to have a large amount of outgoing mail servers. I get the emails from mail##.winvite.com where ## can be any number. The servers so far have followed that pattern though, so is there anything I can do? Thanks, Dave
Hi, you can you my SPAMCONTROL patch which gives you the filter capabilities for: mail##.winvite.com Check: http://www.fehcom.de/qmail_en.html cheers. eh. At 12:58 13.9.2000 -0400, Hubbard, David wrote: >Hi all, > I've got a couple of places that like to >subscribe non-existant email addresses to >mailing lists without confirmation. One of >these bastards is winvite.com. The problem >I'm having is that they don't send their >emails with a "From" header, so control/badmailfrom >with an @winvite.com entry is not blocking >their mail. The other problem is I can't >block them by IP because they seem to have >a large amount of outgoing mail servers. I >get the emails from mail##.winvite.com where >## can be any number. The servers so far have >followed that pattern though, so is there >anything I can do? > >Thanks, > >Dave > +-----------------------------------------------------------------------+ | fff hh http://www.fehcom.de Dr. Erwin Hoffmann | | ff hh | | ff eee hhhh ccc ooo mm mm mm Wiener Weg 8 | | fff ee ee hh hh cc oo oo mmm mm mm 50858 Koeln | | ff ee eee hh hh cc oo oo mm mm mm | | ff eee hh hh cc oo oo mm mm mm Tel 0221 484 4923 | | ff eeee hh hh ccc ooo mm mm mm Fax 0221 484 4924 | +-----------------------------------------------------------------------+
"Hubbard, David" wrote: > > Hi all, > I've got a couple of places that like to > subscribe non-existant email addresses to > mailing lists without confirmation. One of > these bastards is winvite.com. The problem > I'm having is that they don't send their > emails with a "From" header, so control/badmailfrom > with an @winvite.com entry is not blocking > their mail. The other problem is I can't > block them by IP because they seem to have > a large amount of outgoing mail servers. I > get the emails from mail##.winvite.com where > ## can be any number. The servers so far have > followed that pattern though, so is there > anything I can do? I use rblsmtpd, and a local RBL style domain, which allows me to block off whole netblocks with a 'dig' command and a couple of Python scripts. Also allows me to give a customized "middle finger" bounce message to each domain. New spammers can be blocked off within seconds of popping up. Contact me off-list if you'd like more info. Eric
Title: C API for queueing messagesHi All,
We are trying to find out what is the most efficient way of queueing the message in qmail from our C Programs. So, would like to know if there are any C API's that are available for queuing messages. Basically I am looking for library routines that act as the native submission interface(API) for qmail. I would like to use the API's from my C Program that we currently have where we compose and build the messages and to queue the email message directly. Something similar to mail_open() and mail_close() provided by zmailer where you can submit messages composed in the MSG_RFC822 format.I can always call sendmail wrapper for queue-Inject or queue-inject itself from my C program thro a popen() or system() call, but I want to avoid the overhead of starting a new UNIX process for each and every email that we send and also popen() is not very efficient.
Any help will be appreciated. Any other ideas are also most welcome
Thanks and Regards,
- Jay
The only legitimate API is to invoke qmail-queue via the exec() system call. This is because qmail-queue is setuid qmailq. In other words, it provides a security barrier to the queue. If you bypass qmail-queue all your programs that call the API will need to be setuid qmailq thus making your queue vulnerable to all those programs. I don't know how zmailer does it, but qmail, postfix and sendmail all use a set*id program to protect their queue. (Does anyone know whether zmailer does a fork/exec under the covers of the API?) Have you measured that execing qmail-queue is "not very efficient" in the full context of your system or are you surmising this? Note that the full cost of injecting a mail securely on the queue is probably greater than the cost of a fork/exec of qmail-queue so an API that bypasses qmail-queue may not gain you that much. Regards. On Wed, Sep 13, 2000 at 11:58:04AM -0500, Jay Balakrishna wrote: > Hi All, > We are trying to find out what is the most efficient way of queueing the > message in qmail from our C Programs. So, would like to know if there are > any C API's that are available for queuing messages. Basically I am looking > for library routines that act as the native submission interface(API) for > qmail. I would like to use the API's from my C Program that we currently > have where we compose and build the messages and to queue the email message > directly. Something similar to mail_open() and mail_close() provided by > zmailer where you can submit messages composed in the MSG_RFC822 format. > I can always call sendmail wrapper for queue-Inject or queue-inject itself > from my C program thro a popen() or system() call, but I want to avoid the > overhead of starting a new UNIX process for each and every email that we > send and also popen() is not very efficient. > Any help will be appreciated. Any other ideas are also most welcome > Thanks and Regards, > - Jay >
Title: RE: C API for queueing messagesHi,
Replies to your questions below.
>I don't know how zmailer does it, but qmail, postfix and sendmail
>all use a set*id program to protect their queue. (Does anyone know
>whether zmailer does a fork/exec under the covers of the API?)No, it does not do a fork/exec under the covers. From my understanding
of the zmailer code, mail_open() it opens a file under an intermediate
queue directory called router and returns a FILE pointer for us to write the
message. Then a seperate router process picks up the message
from there. The advantage here is that there is very little over head in
writing a file as opposed a popen("sendmail -i -t") call.>Have you measured that execing qmail-queue is "not very efficient" in
>the full context of your system or are you surmising this?Yes, we have done a lot of timing analysis and it was found that in excess
of 50% of the processing time is being spent in the code segment of the
application that invokes the sendmail exe thro popen(). We also explored
the possibilities of using fork(), which is faster. But we are afraid that
the system might run out of ulimit with all these small processes spawned.So now I understand why qmail does not have an API because otherwise
the security is compromised. Thanks for your email.Regards,
- Jay
On Wed, Sep 13, 2000 at 11:58:04AM -0500, Jay Balakrishna wrote:
> Hi All,
> We are trying to find out what is the most efficient way of queueing the
> message in qmail from our C Programs. So, would like to know if there are
> any C API's that are available for queuing messages. Basically I am looking
> for library routines that act as the native submission interface(API) for
> qmail. I would like to use the API's from my C Program that we currently
> have where we compose and build the messages and to queue the email message
> directly. Something similar to mail_open() and mail_close() provided by
> zmailer where you can submit messages composed in the MSG_RFC822 format.
> I can always call sendmail wrapper for queue-Inject or queue-inject itself
> from my C program thro a popen() or system() call, but I want to avoid the
> overhead of starting a new UNIX process for each and every email that we
> send and also popen() is not very efficient.
> Any help will be appreciated. Any other ideas are also most welcome
> Thanks and Regards,
> - Jay
>
On Wed, Sep 13, 2000 at 01:27:57PM -0500, Jay Balakrishna wrote: > Hi, > > Replies to your questions below. > > >I don't know how zmailer does it, but qmail, postfix and sendmail > >all use a set*id program to protect their queue. (Does anyone know > >whether zmailer does a fork/exec under the covers of the API?) > > No, it does not do a fork/exec under the covers. From my understanding > of the zmailer code, mail_open() it opens a file under an intermediate > queue directory called router and returns a FILE pointer for us to write the > message. Then a seperate router process picks up the message > from there. The advantage here is that there is very little over head in > writing a file as opposed a popen("sendmail -i -t") call. > > >Have you measured that execing qmail-queue is "not very efficient" in > >the full context of your system or are you surmising this? > > Yes, we have done a lot of timing analysis and it was found that in excess > of 50% of the processing time is being spent in the code segment of the > application that invokes the sendmail exe thro popen(). Erum, good, but did you measure the *total* cost of the email? That includes the cost of the router process (in the case of zmailer) and the qmail-send process (in the case of qmail) in picking up the email and completing the queuing and delivery cost? Sure, your insertion program may be 50% fork/exec, but if your insertion program is 5% of the total load of the system, then you're trying to tune a 2.5% problem. Actually, I'd expect that sort of outcome regardless of the type of API or mailer, if your program does little more than inject mail. > We also explored > the possibilities of using fork(), which is faster. But we are afraid that > the system might run out of ulimit with all these small processes spawned. That's an interesting conclusion. You see a popen() does exactly the same thing. It fork/execs a shell which then fork/execs qmail-queue, so popen() exacerbates your ulimit fear rather than alleviating it. In other words your explorers need to look again as they got it exactly around the wrong way. As an aside, any ulimit fear is irrelevant if your insertion program waits for the return from qmail-queue before submitting the next mail as the ulimit applies to concurrent processes, not serially created (and destroyed) ones. > So now I understand why qmail does not have an API because otherwise > the security is compromised. Thanks for your email. Not quite. qmail doesn't have an API because no one has written one. That API would simply call qmail-queue under the covers just as the zmailer API calls fopen() under the covers. Regards.
Jay Balakrishna <[EMAIL PROTECTED]> writes: > We are trying to find out what is the most efficient way of queueing the > message in qmail from our C Programs. So, would like to know if there > are any C API's that are available for queuing messages. Basically I am > looking for library routines that act as the native submission > interface(API) for qmail. You're going to need to write your own library, probably as wrappers around pipe opens to qmail-queue. <ftp://ftp.eyrie.org/pub/software/majordomo/mjinject> may be a decent starting point; it's in Perl, but should be possible to convert to C. The queue sub is the one that does what you're trying to do. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Jay Balakrishna writes: > Hi All, > We are trying to find out what is the most efficient way of queueing the > message in qmail from our C Programs. So, would like to know if there are > any C API's that are available for queuing messages. Basically I am looking > for library routines that act as the native submission interface(API) for > qmail. The standard Unix API is to popen sendmail and give it the 't' option. qmail supports that API, although qmail's native submission mechanism is to popen /var/qmail/bin/qmail-inject with the appropriate options. For maximum efficiency and security, create your own envelope and canonical set of headers, fork a copy of qmail-queue and throw them down the two file descriptors. Your program could do exactly the same thing that qmail-queue does, except that qmail-queue has been very carefully to protect internal security. If you're not worried about internal security, then you might want to write some code that does exactly what qmail-queue does. Also, qmail-queue is a documented interface and will be preserved from version to version of qmail. The queue internals are likely to change drastically. -- -russ nelson <[EMAIL PROTECTED]> http://russnelson.com | Crynwr sells support for free software | PGPok | Damn the firewalls! 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Full connectivity ahead! Potsdam, NY 13676-3213 | +1 315 268 9201 FAX |
Hiho! I need to send emails from a host S that uses qmail as a MTA for sending special emails to a special host R that is not known by DNS. Usually the host S sends all his outgoing mail traffic to a mail hub. Our maintenance company says that qmail is unable to send mails to this host in this setting. Is there an easier way, than writing an own mail client that is used by the program on host S that needs to send mails to this special host R, to solve our problem? Bye Arne --- e*Message GmbH OMC ZT FFM, Arne W�rner Sch�nhauser Allee 10-11, 10119 Berlin, Germany phone: +49 69 53089 150 +49 177 5895591 fax: +49 69 53089 159
On Wed, Sep 13, 2000 at 07:06:37PM +0200, [EMAIL PROTECTED] wrote: > I need to send emails from a host S that uses qmail as a MTA for sending > special emails to a special host R that is not known by DNS. Usually the > host S sends all his outgoing mail traffic to a mail hub. > > Our maintenance company says that qmail is unable to send mails to this > host in this setting. > > Is there an easier way, than writing an own mail client that is used by the > program on host S that needs to send mails to this special host R, to solve > our problem? See the qmail-remote man page, and look for "smtproutes." Chris
[EMAIL PROTECTED] wrote: >I need to send emails from a host S that uses qmail as a MTA for sending >special emails to a special host R that is not known by DNS. Usually the >host S sends all his outgoing mail traffic to a mail hub. > >Our maintenance company says that qmail is unable to send mails to this >host in this setting. > >Is there an easier way, than writing an own mail client that is used by the >program on host S that needs to send mails to this special host R, to solve >our problem? Yeah, put an entry for R in control/smtproutes (see "man qmail-remote"). E.g., if R is r.example.com with IP address 10.11.12.13, add an entry like: r.example.com:[10.11.12.13] and all mail addressed to [EMAIL PROTECTED] will be sent to 10.11.12.13. -Dave
On Wed, Sep 13, 2000 at 07:06:37PM +0200, [EMAIL PROTECTED] wrote: > Hiho! > > I need to send emails from a host S that uses qmail as a MTA for sending > special emails to a special host R that is not known by DNS. Usually the > host S sends all his outgoing mail traffic to a mail hub. > > Our maintenance company says that qmail is unable to send mails to this > host in this setting. Get yourself a better maintenance company. Check the qmail-remote man pages regarding smtproutes for a trivial way to do this. Regards. > > Is there an easier way, than writing an own mail client that is used by the > program on host S that needs to send mails to this special host R, to solve > our problem? > > Bye > Arne > --- > e*Message GmbH > OMC ZT FFM, Arne W�rner > Sch�nhauser Allee 10-11, 10119 Berlin, Germany > phone: +49 69 53089 150 +49 177 5895591 fax: +49 69 53089 159 >
If ----- Original Message ----- From: "Dave Sill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 12:37 PM Subject: Re: hosts not known by DNS If the email accounts are on host R and R itself isn't known by DNS then you will need to address the in the format of user@[10.11.12.13]. Of course I didn't fully understand the question upon first reading so may be off-base here. dG > [EMAIL PROTECTED] wrote: > > >I need to send emails from a host S that uses qmail as a MTA for sending > >special emails to a special host R that is not known by DNS. Usually the > >host S sends all his outgoing mail traffic to a mail hub. > > > >Our maintenance company says that qmail is unable to send mails to this > >host in this setting. > > > >Is there an easier way, than writing an own mail client that is used by the > >program on host S that needs to send mails to this special host R, to solve > >our problem? > > Yeah, put an entry for R in control/smtproutes (see "man > qmail-remote"). E.g., if R is r.example.com with IP address > 10.11.12.13, add an entry like: > > r.example.com:[10.11.12.13] > > and all mail addressed to [EMAIL PROTECTED] will be sent to > 10.11.12.13. > > -Dave
On 13 06, [EMAIL PROTECTED] wrote: # Hiho! # # I need to send emails from a host S that uses qmail as a MTA for sending # special emails to a special host R that is not known by DNS. Usually the # host S sends all his outgoing mail traffic to a mail hub. # # Our maintenance company says that qmail is unable to send mails to this # host in this setting. # # Is there an easier way, than writing an own mail client that is used by the # program on host S that needs to send mails to this special host R, to solve # our problem? # # Bye # Arne Here's a simple way in your smtproutes file in /var/qmail/control (if there is no such file create it) add the line R:<ip address of R> :<mail router> -- Justin Bell
Hi, When I try to send mail from Netscape MUA to [EMAIL PROTECTED], it shows an error message " The mail server responded: sorry, that domain isn't in my list of allowed rcphosts. Please check the message receipients and try again" If I add the xyz.com in the rcphosts and it works. My question is how can I edit this file (by addind all the domain? Noooooo) or there is better way I can do about it? Thanks for your time. Regards, Jerry
On 13-Sep-2000, Jerry Hsieh wrote: > " The mail server responded: sorry, that domain isn't in my list of allowed > rcphosts. Please check the message receipients and try again" > > If I add the xyz.com in the rcphosts and it works. My question is how can I > edit this file (by addind all the domain? Noooooo) or there is better way I > can do about it? Thanks for your time. You need to tell your qmail that your machine (and probably other authorized machines on your network) is allowed to relay mails. The most common way to do this is by using tcpserver. http://www.palomine.net/qmail/relaying.html By adding the domain to rcpthosts (NOT rcphosts!), you're essentially allowing ANYBODY to relay to that particular domain using your machine, e.g. I can use your machine to send spam to that domain. Ronny
In no particular order... 1) I wrote a newbie-friendly qmail guide called "Life with qmail". It's available from http://lwq.w3.to, which is a shortcut for http://Web.InfoAve.Net/~dsill/lwq.html. I strongly recommend reading it before you continue trying to install qmail. 2) Regardless of whether you prefer RPM installations, there are good reasons to install qmail from source. These are documented in LWQ: http://Web.InfoAve.Net/~dsill/lwq.html#installation-issues 3) You claim to be--and by all appearances *are*--a Linux newbie. Yet you also seem to be running a web site aimed at telling other newbies how to run Linux systems (linuxpeople.cc). Is this not the blind leading the blind? I don't mean to sound elitist, but you really ought to get a few of the basics (such as the concept of the shell executable path) down first. 4) You're trying too hard. Stop posting so frantically. Take a few breaths, dig around your system and the available documentation a little more, and contemplate the responses to your postings. This list is fast, but it's not realtime like IRC. If you wait a while for responses, sometimes better ones than those that arrived first will appear. 5) You're too thin-skinned. So a couple people found you annoying and insulted you. So what? Get over it. 6) Why do you hide your identity? Your messages are from "[EMAIL PROTECTED]". You don't sign them with even a first name. Your web site doesn't give any clues, either. It's no big deal, but it *is* kind of annoying. 7) If a compile fails because some include file can't be found, it's useful to see if a file by the same name resides on your system, *but* it's not generally a good idea to assume that all files with the same name have the same contents. Therefore, copying/linking found files to the expected location is *not* the right way to fix the problem. 8) "The" qmail web site is http://pobox.com/~djb/qmail.html. www.qmail.org is also a great qmail resource, but it's not run by the author of qmail. The fact that it links to RPM's doesn't mean the author of qmail endorses RPM distributions of qmail. 9) Regarding the posting of the output of "ls" in the source directory... That *was* annoying, and even the newbiest of newbies should realize that listing the contents of a large, freshly unpacked tar file is unnecessary. And it wasn't "source code" as you claimed in a later message, it was a directory listing. 10) A '486 with 8 MB RAM and 500 MB is pretty pathetic. You shouldn't be surprised if it's a little harder than usual to work with such a system. I though my 60 MHz Pentium was pitiful, but it's got gobs more memory and disk (32 MB and 1 GB). Well, that should do for a start. Please don't be offended: there are many people on this list who will bend over backwards to help you...if you're willing to let them. -Dave
Dave Sill wrote: > In no particular order... <trim> Hooray, Dave! Now THAT was a classy response. Cheers to you. I'm glad there are people out there who can still be helpful and understanding in spite of all the ranting and raving that goes on in mailing lists. And yes, LWQ is pretty sweet. =) -Stephen-
Quoting Jay Balakrishna ([EMAIL PROTECTED]): [...] > Any help will be appreciated. Any other ideas are also most welcome > Thanks and Regards, Wow, Mypoints! I think Mark is helping admirably with your question, but I will offer some help myself in another area that Mypoints needs assistance: I will write a program to collect your bounces and weed the stale addresses from your mailing lists--because you never do! I've complained for a year and a half that you don't--I finally just firewalled your network at our border router a month ago (phone calls to mypoints gave me a run-around), yet still I see rejected packets from your various mail servers. None of our customers can get to your web site, so it's unlikely they are signing up (and I assume, hope rather, that third-parties can't sign them up without you sending email confirmation, hmm?). (OK, I'm not really meaning to air dirty laundry, but this is sort of qmail-related in an abstract way ;-), and like I said their network is blackholed by us and phone calls have been useless.) Since mypoints.com sends email with invalid return paths, such as "[EMAIL PROTECTED]", our mail servers can't _ever_ deliver bounces back to them, and their administration team seems quite unwilling to fix it, despite my numerous recommendations to do so. I once found around 40 (!!) bounces queued for various unreachable mlbx*.mypoints.com servers. I'll bet this would be a pet peeve for many of you as well. The entire world does not run sendmail, nor does the entire world reject invalid addresses during SMTP negotiation. Treating the world like everyone does those things is not very net-friendly. Not only that, but I am taking a wild guess that your sendmail MTAs are starting to break under the load. If you took some steps to reduce your outbound mail queues, like removing the large number of invalid addresses to which you attempt delivery, you may see improved performance. (goodness, I can't even imagine how many AOL'ers have signed up for mypoints and who's mail is now bouncing, could be thousands and thousands. We're small and had 40!) I hope that now, because someone at mypoints.com is asking about qmail (perhaps even switching outbound mail to use qmail?), they will feel a little more willing to accomodate those of us who happily use said MTA on our own servers. Certainly, if *I* can be of any assistance personally, please let me know (of course, that would probably depend on me removing that acl, which I won't without getting some satisfaction ;-) regards, -- Aaron L. Meehan [EMAIL PROTECTED] System Administrator Central Oregon Internet http://www.coinet.com/
you should feel lucky to only have 40 in your queue. after a quick check i find 390 in the queue on just *1* of many inbound servers. i had noticed the numerous bounces not making it home and just hadn't got around to complaining to them yet. it appears that they don't care anyway. pitty i may just have to block them too. mike. > -----Original Message----- > From: Aaron L. Meehan [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 13, 2000 12:40 PM > To: '[EMAIL PROTECTED]' > Subject: Mypoints.com is not nice to us qmail admins (was: C API for > queueing messages) > > > Quoting Jay Balakrishna ([EMAIL PROTECTED]): > [...] > > Any help will be appreciated. Any other ideas are also most welcome > > Thanks and Regards, > > Wow, Mypoints! > > I think Mark is helping admirably with your question, but I will offer > some help myself in another area that Mypoints needs assistance: > > I will write a program to collect your bounces and weed the stale > addresses from your mailing lists--because you never do! I've > complained for a year and a half that you don't--I finally just > firewalled your network at our border router a month ago (phone calls > to mypoints gave me a run-around), yet still I see rejected packets > from your various mail servers. None of our customers can get to your > web site, so it's unlikely they are signing up (and I assume, hope > rather, that third-parties can't sign them up without you sending > email confirmation, hmm?). > > (OK, I'm not really meaning to air dirty laundry, but this is sort of > qmail-related in an abstract way ;-), and like I said their network is > blackholed by us and phone calls have been useless.) > > Since mypoints.com sends email with invalid return paths, such as > "[EMAIL PROTECTED]", our mail servers can't _ever_ deliver > bounces back to them, and their administration team seems quite > unwilling to fix it, despite my numerous recommendations to do so. I > once found around 40 (!!) bounces queued for various unreachable > mlbx*.mypoints.com servers. I'll bet this would be a pet peeve for > many of you as well. >
"Aaron L. Meehan" wrote: > > Quoting Jay Balakrishna ([EMAIL PROTECTED]): > [...] > > Any help will be appreciated. Any other ideas are also most welcome > > Thanks and Regards, > > Wow, Mypoints! > > I think Mark is helping admirably with your question, but I will offer > some help myself in another area that Mypoints needs assistance: > > I will write a program to collect your bounces and weed the stale > addresses from your mailing lists--because you never do! [snip.] Got it. Mypoints.com == Evil and/or clueless spammer. Adding their netblock to personal RBL domain now... Call me an ultra hair-trigger reactionary, but I just have no tolerance for spammers of any stripe, and I figure the more IPs in my RBL-style domain, the cleaner and more manageable my mail queues will be... Eric
I have been trying to setup RBL and DUL on our servers in the last 2 days. I have RBL working just fine, and DUL is also working. The problem is a few of our class C's from our netblock have been listed in the DUL. Which this is not really a big deal i just have to set the $RBLSMTPD variable to accept mail from those IP's. Well so i thought, no matter if that variable is set or not those hosts are denied access. I have tried just everything i can think of, read all the docs that i have found, followed them to the letter and still no luck. We are running qmail-1.03 and ucspi-tcp-0.88. Did something change in the way rblsmtpd is setup and the docs don't reflect this change? here are the scripts i use for tcpserver and a output of a telnet session to port 25. Any help would be greatly appericated! rc.rblsmtpd ----------- #!/bin/sh TCPSERVER="/usr/local/bin/tcpserver" SPLOGGER="/var/qmail/bin/splogger" WRAPPER="/var/qmail/bin/rblsmtpd-wrapper" TCPRULES="/etc/tcprules.cdb" LOGFILE="/var/log/tcpserver-smtp.log" HOSTNAME="mail2.networkone.net" PORT=25 MAXCONNS=120 SUID=301 SGID=101 $TCPSERVER -v -c $MAXCONNS -x $TCPRULES -u $SUID -g $SGID \ -p -l $HOSTNAME 0 $PORT $WRAPPER 2> $LOGFILE & rblsmtpd-wrapper ---------------- #!/bin/sh DUL="dialups.mail-abuse.org" RBL="rbl.maps.vix.com" SPLOGGER="/var/qmail/bin/splogger" SMTPD="/var/qmail/bin/qmail-smtpd" RBLSMTPD="/usr/local/bin/rblsmtpd -r$DUL -r$RBL" echo "SMTP connect from $TCPREMOTEHOST ($TCPREMOTEIP)" | $SPLOGGER qmail-smtpd exec $RBLSMTPD $SMTPD tcprules.txt ------------ one of the entries in question, which i have tried several differnet ways 209.144.118.:allow,RELAYCLIENT="",RBLSMTPD="",REASON="Local Dialup" output of telnet session to port 25 ----------------------------------- telnet mail2.networkone.net 25 Trying 209.144.121.9... Connected to mail2.networkone.net. Escape character is '^]'. 220 rblsmtpd.local 451 /usr/local/bin/rblsmtpd -rdialups.mail-abuse.org -rrbl.maps.vix.com quit 221 rblsmtpd.local Connection closed by foreign host. Chris Scheller Network One Internet, inc. http://www.networkone.net/ System/Network Administration 1-888-GOT-NET1
On Wed, Sep 13, 2000 at 01:40:20PM -0700, Chris Scheller wrote: > I have been trying to setup RBL and DUL on our servers in the last 2 days. I > have RBL working just fine, and DUL is also working. The problem is a few > of our class C's from our netblock have been listed in the DUL. Which this is > not really a big deal i just have to set the $RBLSMTPD variable to accept > mail from those IP's. Well so i thought, no matter if that variable is set or > not those hosts are denied access. I have tried just everything i can think of, > read all the docs that i have found, followed them to the letter and still > no luck. We are running qmail-1.03 and ucspi-tcp-0.88. Did something change > in the way rblsmtpd is setup and the docs don't reflect this change? > here are the scripts i use for tcpserver and a output of a telnet session to > port 25. Any help would be greatly appericated! > > rc.rblsmtpd > ----------- > #!/bin/sh > > TCPSERVER="/usr/local/bin/tcpserver" > SPLOGGER="/var/qmail/bin/splogger" > WRAPPER="/var/qmail/bin/rblsmtpd-wrapper" > TCPRULES="/etc/tcprules.cdb" > LOGFILE="/var/log/tcpserver-smtp.log" > HOSTNAME="mail2.networkone.net" > PORT=25 > MAXCONNS=120 > SUID=301 > SGID=101 > > $TCPSERVER -v -c $MAXCONNS -x $TCPRULES -u $SUID -g $SGID \ > -p -l $HOSTNAME 0 $PORT $WRAPPER 2> $LOGFILE & > > rblsmtpd-wrapper > ---------------- > #!/bin/sh > > DUL="dialups.mail-abuse.org" > RBL="rbl.maps.vix.com" > SPLOGGER="/var/qmail/bin/splogger" > SMTPD="/var/qmail/bin/qmail-smtpd" > RBLSMTPD="/usr/local/bin/rblsmtpd -r$DUL -r$RBL" ^^^^^^^^ Try calling this something else, like RBLPROGRAM or something. It conflicts with the RBLSMTPD that you're trying to set in your rules file. Chris
> > RBLSMTPD="/usr/local/bin/rblsmtpd -r$DUL -r$RBL" > ^^^^^^^^ > Try calling this something else, like RBLPROGRAM or something. It conflicts > with the RBLSMTPD that you're trying to set in your rules file. i could kick myself, as a matter of fact i think i will! :) i stare at this all day and it doesn't dawn on me! thanks for help, it is working now! Chris Scheller Network One Internet, inc. http://www.networkone.net/ System/Network Administration 1-888-GOT-NET1
In the immortal words of John White ([EMAIL PROTECTED]): > > However, I question the decision to use Solaris x86. I'm not aware > of any advantage there is over something like Linux or xBSD. Three words: journalling file system. Four more words: integrated logical volume manager. Solstice DiskSuite may not be a best-of-breed product in either of those categories, but it's there, it's basically stable, it's documented, and as of Solaris 7 it's part of the base distribution. I'm not a big fan of Solaris/Intel myself, but in a production environment, a reliable and flexible filesystem is a dealbreaker. -n ------------------------------------------------------------<[EMAIL PROTECTED]> "I've yet to read about an ex-lesbian who, upon accepting Jesus Christ as her personal savior, was seized by a sudden and overwhelming desire to chew through Matt Damon's underpants." (--Dan Savage) <http://www.blank.org/memory/>------------------------------------------------
On Wed, Sep 13, 2000 at 04:56:28PM -0400, Nathan J. Mehl wrote: > In the immortal words of John White ([EMAIL PROTECTED]): > > > > However, I question the decision to use Solaris x86. I'm not aware > > of any advantage there is over something like Linux or xBSD. > > Three words: journalling file system. > > Four more words: integrated logical volume manager. > > Solstice DiskSuite may not be a best-of-breed product in either of > those categories, but it's there, it's basically stable, it's > documented, and as of Solaris 7 it's part of the base distribution. Solaris 7 definitely doesn't come with DiskSuite as part of the base distribution. I know that I certainly don't have it. Solaris 7 does come with a FS that journals metadata, but no one's ever benchmarked it's performance with a large todo for the list. John
In the immortal words of John White ([EMAIL PROTECTED]): > > Solaris 7 definitely doesn't come with DiskSuite as part of the > base distribution. I know that I certainly don't have it. Hrm. Okay, I could have sworn that 2.7 was being bundled with DiskSuite, but I don't have a media package around me that I can verify that with. I _can_ verify that the current Binary License for Solaris 8 does appear to include SDS bundled with it. > Solaris 7 does come with a FS that journals metadata, but no one's > ever benchmarked it's performance with a large todo for the list. Well, like I said, it's not necessarily best-of-breed, it's just there, which is a big win over the various free unixes if you're working on a constrained hardware budget. In 1-2 years, when reiserfs/xfs/jfs/ext3 or whatever is integrated into the mainline linux distributions, this will become much less of an issue. (Doesn't really address that LVM portion, but that's probably a lot less critical for most people.) -n --------------------------------------------------------------<[EMAIL PROTECTED]> "Two crucial things in New York: Do the work and enjoy the town. New York furnishes vast pleasure to them what can hear the music and do the dance. They may be from Wisconsin or Denmark or Japan, but they walk down the street and it appeals to them, the hurly-burly and the eccentrics and the street musicians, the aroma of pizza and chestnuts and hot dogs, the jangle of a dozen different languages, the distant siren, the rumble of the subway, the pockets of grace and elegance and the flash and hustle and the river of perspiring humanity. A person who knows how to make himself happy can do well in New York. Enjoying the carnival is more important to your happiness than "making it." But do do the work." (--Garrison Keillor) <http://www.blank.org/memory/>--------------------------------------------------
Thus spake Nathan J. Mehl ([EMAIL PROTECTED]): > > Solaris 7 does come with a FS that journals metadata, but no one's > > ever benchmarked it's performance with a large todo for the list. > Well, like I said, it's not necessarily best-of-breed, it's just > there, which is a big win over the various free unixes if you're > working on a constrained hardware budget. Can you please expand on how an inferior file system for Solaris is in any way "a big win over the various free unixes"? Especially under the assumption of a constrained budget, please. > In 1-2 years, when reiserfs/xfs/jfs/ext3 or whatever is integrated > into the mainline linux distributions, this will become much less of > an issue. (Doesn't really address that LVM portion, but that's > probably a lot less critical for most people.) Who cares about "mainstream linux distributions"? Felix
In the immortal words of Felix von Leitner ([EMAIL PROTECTED]): > Thus spake Nathan J. Mehl ([EMAIL PROTECTED]): > > > Solaris 7 does come with a FS that journals metadata, but no one's > > > ever benchmarked it's performance with a large todo for the list. > > Well, like I said, it's not necessarily best-of-breed, it's just > > there, which is a big win over the various free unixes if you're > > working on a constrained hardware budget. > > Can you please expand on how an inferior file system for Solaris is in > any way "a big win over the various free unixes"? Especially under the > assumption of a constrained budget, please. Could we please dispense with the flamebait? I think I've been pretty clear here: _IF_ you have an environment where filesystem integrity in case of power loss or other catastrophe is paramount, a journalling filesystem is probably going to be a requirement. Solaris X86 happens to offer it, bundled into the core operating system, and is currently free (as in dollars) for most uses. If you have an environment where read/write performance is critical, but reliability isn't, you've got... well, actually what you've got is a nice leadin to the eternal "ext2 vs ffs" debate, which is even more off-topic. Let's just say you've got plenty of options. Have fun. If reliability, flexibility _and_ speed are paramount, you're probably running VXFS+VXVM already, and long-since stopped paying attention to this discussion. (You're probably also not even considering low-end x86 hardware in the first place.) > Who cares about "mainstream linux distributions"? I'm not trying to advocate a particular OS here. Somebody asked why one might want to use Solaris x86 instead of linux and I offered a hypothesis. If that happened to tickle some odd sensitivity of yours, that was not my intention, but nor is it my concern. -n ------------------------------------------------------------<[EMAIL PROTECTED]> "There are certain phrases that inspire an instinctive dread in moviegoers: `Tarantino-esque'; `big in France'; `starring Andy Garcia.'" (--M.E. Williams) <http://www.blank.org/memory/>------------------------------------------------
Thus spake Nathan J. Mehl ([EMAIL PROTECTED]): > > Can you please expand on how an inferior file system for Solaris is in > > any way "a big win over the various free unixes"? Especially under the > > assumption of a constrained budget, please. > Could we please dispense with the flamebait? The inferiority was noted by yourself, so I don't see a flamebait here. > I think I've been pretty clear here: _IF_ you have an environment > where filesystem integrity in case of power loss or other catastrophe > is paramount, a journalling filesystem is probably going to be a > requirement. Solaris X86 happens to offer it, bundled into the core > operating system, and is currently free (as in dollars) for most uses. Solaris X86 also happens to support very little mainstream hardware, is an order of magnitude slower than Linux on the same hardware, and the filesystem sucks by tradition -- with or without journaling. As you might know, the journaling code is new in Solaris 7. Previously, Sun would offer licensed code from another vendor (Veritas AFAIK). You wouldn't actually recommend new Sun code to anyone for reliability reasons, would you? Besides, what makes you claim that there is no journaling for free unices? > > Who cares about "mainstream linux distributions"? > I'm not trying to advocate a particular OS here. I'm not complaining about the Linux here, but about the mainstream distributions part. Felix
Thus spake Nathan J. Mehl ([EMAIL PROTECTED]): > In 1-2 years, when reiserfs/xfs/jfs/ext3 or whatever is integrated > into the mainline linux distributions, this will become much less of > an issue. (Doesn't really address that LVM portion, but that's > probably a lot less critical for most people.) reiserfs is available for many distributions. But even if not, it should not take more than half an hour on decent machines to patch a decent kernel and run the a new kernel with reiserfs included. If you want LVM under linux, take a look of SuSE�s work on that issue. It basically feels like the LVM on HPUX 10.X and is available _now_. Give it a try. cheers, oec
In the immortal words of Felix von Leitner ([EMAIL PROTECTED]): > > The inferiority was noted by yourself, so I don't see a flamebait here. I think you're reading a little too much into what I'm saying. "Not as good as veritas" is a far cry from "inferior," and is still a long sight better than "only available as unstable patch sets." Match your tools to your task: not everybody needs a gold-plated hammer to pound in penny nails, nor is everybody interested in forging their own steel. > As you might know, the journaling code is new in Solaris 7. Solaris 7 is about two years old now. Ahem. > Previously, Sun would offer licensed code from another vendor > (Veritas AFAIK). Actually, no. Sun has always had two JFS/LVM products, targeted at different markets. Solstice DiskSuite (which was part of the "server" licenses for Solaris going back at least to 2.4) was an internally developed solution targeted at low- to mid-range servers. For high-end requirements (e.g. database hosting), they OEMed Veritas' VXFS/VXVM product. > You wouldn't actually recommend new Sun code to anyone for > reliability reasons, would you? As far as I am aware, the journalling code in 2.7 is simply the "metatrans" code from DiskSuite, slightly tweaked (the log gets stuck into the filesystem root-reserved space instead of onto a dedicated partition) and bundled into the core OS. And DiskSuite has been around forever and a day. > Besides, what makes you claim that there is no journaling for free > unices? I claim no such thing. There are plenty of them, none of which are anywhere near production-quality. (Hans Reiser would disagree I guess, but I will content myself with knowing that Linus and Alan do not.) That will change with time. This conversation has veered into the silly and completely off-topic; I will no longer cc the list at this point. -n ------------------------------------------------------<[EMAIL PROTECTED]> "Bedford has never ever heard of Salvador Dali. Which is perfectly all right. Salvador Dali and fifty cents will get you a cup of clock melt." <http://www.blank.org/memory/>------------------------------------------
In the immortal words of Oezguer Kesim ([EMAIL PROTECTED]): > > reiserfs is available for many distributions. But even if not, it should > not take more than half an hour on decent machines to patch a decent kernel > and run the a new kernel with reiserfs included. Honestly, I can't consider reiserfs to be production quality yet. I really would prefer not to open that can of worms on this list though; let's just say that reasonable people can disagree about that and that we're all looking foward to the day when it's part of the standard kernel. > If you want LVM under linux, take a look of SuSE�s work on that issue. It > basically feels like the LVM on HPUX 10.X and is available _now_. Hm, thanks for the pointer. SuSE's tools don't get anywhere near as much exposure as they should on this side of the pond... -n ------------------------------------------------------------<[EMAIL PROTECTED]> "Rand dealt with that by blandly ignoring the issue. She never had kids, and I doubt very much that she ever gave them a moment's thought. Too inconvenient. That messy reality thing, you know? It's much more fun to write 800-page superhero comic books and then declare them by fiat to be an accurate description of reality. It helps to have disciples who'll tell you you're not a psychopath." (--80md) <http://www.blank.org/memory/>------------------------------------------------
I have been searching the archives to no avail, My mailserver running qmail-1.03 has started creating lots of qmail-queue processes to the point where it chokes any incoming email. I have gone through the log files and cannot find anything that looks funny. I see a huge amount of zero size files in the queue/mess/* directories with no corresponding info or local or remote files. I have stopped qmail, cleaned the zero files out, started qmail. Everything works great, until this process starts all over, zero size files appearring in the mess directories and qmail-queue start amassing and the server chokes. If anyone has any info on why this occurs and how to correct it, please let me know, thank you. -- Sean Peterson System Administrator Valley Internet Providers Ltd. [EMAIL PROTECTED]
On Wed, Sep 13, 2000 at 02:53:07PM -0700, Sean Peterson wrote: > I have been searching the archives to no avail, > > My mailserver running qmail-1.03 has started creating lots of > qmail-queue processes to the point where it chokes any incoming email. I > have gone through the log files and cannot find anything that looks > funny. I see a huge amount of zero size files in the queue/mess/* > directories with no corresponding info or local or remote files. > > I have stopped qmail, cleaned the zero files out, started qmail. > Everything works great, until this process starts all over, zero size > files appearring in the mess directories and qmail-queue start amassing > and the server chokes. > > If anyone has any info on why this occurs and how to correct it, please > let me know, thank you. How old are these processes? Are they all originating from an smtp connection? What does a system call trace (strace, truss, etc) on the qmail-queue processes shows? Are they sitting on a read()? How many is a "huge amount"? Is it larger than the number of qmail-queue processes? Could it be a DOS on your SMTP port(s)? Regards.
> Could it be a DOS on your SMTP port(s)? Perhaps an elaboration is in order. If you go: telnet yoursmtpserver smtp mail from: <me> rcpt to: <me> data and leave it there without closing the connection or completing the SMTP transaction, you will have a situation pretty similar to the one you describe; a qmail-queue process that sits around until qmail-smtpd times out and a zero length file in mess/* and no files elsewhere. I don't necessarily mean a malicious DOS. It may be a lame SMTP client getting confused at the same point in the transaction and subsequently getting wedged for some reason. Regards.
Right, I recall reading that from the archives. How does one go about either, denying the problem mailer from sending email or changing qmail to deal with it in the right way? -- Sean Peterson System Administrator Valley Internet Providers Ltd. [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: > > > Could it be a DOS on your SMTP port(s)? > > Perhaps an elaboration is in order. If you go: > > telnet yoursmtpserver smtp > mail from: <me> > rcpt to: <me> > data > > and leave it there without closing the connection or completing > the SMTP transaction, you will have a situation pretty similar to > the one you describe; a qmail-queue process that sits around until > qmail-smtpd times out and a zero length file in mess/* and no files > elsewhere. > > I don't necessarily mean a malicious DOS. It may be a lame SMTP client > getting confused at the same point in the transaction and subsequently > getting wedged for some reason. > > Regards.
On Wed, Sep 13, 2000 at 03:35:09PM -0700, Sean Peterson wrote: > Right, I recall reading that from the archives. How does one go about > either, > > denying the problem mailer from sending email > > or > > changing qmail to deal with it in the right way? If you can figure out from your tcpserver logs which IP is doing it, you can add a 'deny' to your tcp rules. Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
On Wed, Sep 13, 2000 at 03:35:09PM -0700, Sean Peterson wrote: > Right, I recall reading that from the archives. How does one go about > either, > > denying the problem mailer from sending email Others have pointed out that you can use tcpserver to deny that connection if that's possible (it might be a customer dialup address). > or > > changing qmail to deal with it in the right way? What's the "right way"? qmail deals with it by giving the other end 1200 seconds (by default, but check the qmail-smtpd manpage) to send data, if it doesn't see any data in that time, qmail-smtpd exits, qmail-queue exits, the mess/* file is removed. Essentially you have the problem of deciding whether it's a good client, a bad client or a slow client. In many cases, they are indistingushable. Regards.
Thanks, I appreciated the help. I will let you know what I can find out. Thanks again. -- Sean Peterson System Administrator Valley Internet Providers Ltd. [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: > > On Wed, Sep 13, 2000 at 03:35:09PM -0700, Sean Peterson wrote: > > Right, I recall reading that from the archives. How does one go about > > either, > > > > denying the problem mailer from sending email > > Others have pointed out that you can use tcpserver to deny that > connection if that's possible (it might be a customer dialup address). > > > or > > > > changing qmail to deal with it in the right way? > > What's the "right way"? qmail deals with it by giving the other end > 1200 seconds (by default, but check the qmail-smtpd manpage) to send data, > if it doesn't see any data in that time, qmail-smtpd exits, qmail-queue > exits, the mess/* file is removed. > > Essentially you have the problem of deciding whether it's a good > client, a bad client or a slow client. In many cases, they are > indistingushable. > > Regards.
>My mailserver running qmail-1.03 has started creating lots of >qmail-queue processes to the point where it chokes any incoming email. I >have gone through the log files and cannot find anything that looks >funny. I see a huge amount of zero size files in the queue/mess/* >directories with no corresponding info or local or remote files. Sean, Could it be broken SMTP clients or servers sending bare LFs? I've had a similar problem - see my thread starting on 23rd July, entitled, Solaris / DoS / Broken bare LF mailers / thousands of qmail-smtpd&qmail-queue procs ..In my case, fixing bare LFs sorted out the problem - using fixcr or fixcrio. For what it's worth, a reminder of using fixcr - aimed primarily at archive users who come across this message a month/year etc. ahead and want to see if this might fix similar issues for them... - on the normal tcpserver line for qmail-smtpd, replace qmail-smtpd with sh -c "fixcr | qmail-smtpd" I presume for fixcrio you'd just need fixcrio qmail-smtpd cheers, Andrew.
Hey... I was thinking of uninstalling and reinstalling qmail so I could get even more familiar with it. If get rid of /var/qmail and edit the boot scripts I should be OK right? oh... also the /services dir and all of the qmail users and groups... would that work OK? shawn -- got root?
On Wed, Sep 13, 2000 at 06:02:31PM -0400, shawn p . duffy wrote: > I was thinking of uninstalling and reinstalling qmail so I could get even more > familiar with it. If get rid of /var/qmail and edit the boot scripts I should > be OK right? oh... also the /services dir and all of the qmail users and > groups... That should be fine... Although there really isn't much reason to do that. You can install right over the top of an existing install without any problems. Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
In the immortal words of shawn p . duffy ([EMAIL PROTECTED]): > Hey... > I was thinking of uninstalling and reinstalling qmail so I could get even more > familiar with it. If get rid of /var/qmail and edit the boot scripts I should > be OK right? oh... also the /services dir and all of the qmail users and > groups... > > would that work OK? You shouldn't have to remove the entire services dir -- just the entries for qmail-smtpd and qmail-send should do the trick. Watch out for qmail's "sendmail" wrapper, which might still be lying around in /usr/lib or /usr/sbin. -n ------------------------------------------------------------<[EMAIL PROTECTED]> Toward the end of my career in porn, I reached a point where what I saw every day didn't affect me anymore. Not because I was desensitized or had lost my compassion -- I think it was actually the opposite. I began to see just the people, without judgment, without trying to make any sense out of it. I stopped thinking the actors had to be damaged to do what they did. They were having sex for a living, instead of working in a bank. The bank thing probably takes it's own kind of toll. I wouldn't know. (--Barbara Nitke) <http://www.blank.org/memory/>------------------------------------------------
Dear gentleman, i have just installed qmail in my freebsd box, but after request qmail to send my message, i got my box reboot. At a first look, the machine is not supposed to be reboot under a software error, if it does it is an operating system problem matter. FreeBSD is well known for its rock solid performance, but i am really confused since another server running linux do the job very well. This reboot only happens when i send MANY message to a domain outside my box one, all local messages are delivered very well. My qmail version is 1.03 here goes my uname -a: grios@etosha:~$ uname -a FreeBSD etosha 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 root@etosha:/usr/obj/usr/src/sys/ETOSHA i386 All i got in /var/log/messages is (only the part pertinent to qmail) Sep 13 17:12:21 etosha /kernel: pid 3197 (qmail-remote), uid 1008: exited on sig nal 11 my dmesg is:Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 root@etosha:/usr/obj/usr/src/sys/ETOSHA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping = 4 Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX > real memory = 134217728 (131072K bytes) avail memory = 127643648 (124652K bytes) Preloaded elf kernel "kernel" at 0xc030c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030c09c. Preloaded elf module "vesa.ko" at 0xc030c0ec. grios@etosha:/var/log$ /sbin/dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 root@etosha:/usr/obj/usr/src/sys/ETOSHA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping = 4 Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX> real memory = 134217728 (131072K bytes) avail memory = 127643648 (124652K bytes) Preloaded elf kernel "kernel" at 0xc030c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030c09c. Preloaded elf module "vesa.ko" at 0xc030c0ec. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc00c6d9d (c0006d9d) VESA: Diamond Multimedia Systems, Inc. Pentium Pro MTRR support enabled apm0: <APM BIOS> on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci1: <S3 ViRGE GX2 graphics accelerator> at 0.0 irq 11 isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 12 chip1: <Intel 82371AB Power management controller> port 0x5000-0x500f at device 7.3 on pci0 ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xe400-0xe4ff mem 0xe9000000-0xe9000fff irq 11 at device 11.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs isa0: too many dependant configs (8) isa0: unexpected small tag 14 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: <System console> on isa0 sc0: VGA <10 virtual consoles, flags=0x200> sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 4 on isa0 sio2: type 16550A ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: <HEWLETT-PACKARD DESKJET 610C> MLC,PCL,PML lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:00:21:6c:8f:e0, type NE2000 (16 bit) sbc0: <Creative SB AWE64> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: <SB DSP 4.16> on sbc0 unknown0: <Game> at port 0x200-0x207 on isa0 unknown1: <WaveTable> at port 0x620-0x623 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, unlimited logging ad0: 8063MB <QUANTUM FIREBALL SE8.4A> [16383/16/63] at ata0-master using UDMA33 afd0: 96MB <IOMEGA ZIP 100 ATAPI Floppy> [96/64/32] at ata1-master using PIO0 acd0: CDROM <34X CD-ROM> at ata1-slave using UDMA33 Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 6 lun 0 da0: <QUANTUM VIKING II 9.1WSE 5520> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8709MB (17836668 512 byte sectors: 64H 32S/T 8709C) WARNING: / was not properly dismounted I am really confused how this error could reboot my box, since i have no knowledge on freebsd internals. Everything i did to send message was: grios@etosha:~/personal$ ./mail [EMAIL PROTECTED] <~guest/teste_mail.txt And the source code for mail.c is: grios@etosha:~/personal$ more mail.c #include <stdio.h> #define MAIL_BINARY "/usr/bin/mail" int main(int argc, char *argv[]) { FILE *out; char buffer[255], input[50000]; int count; sprintf(buffer, "%s %64s", MAIL_BINARY, argv[1]); out = popen(buffer, "w"); fprintf(out, "\bContent-Type: multipart-mixed;\nboundary=\"---1234567890df \";\n"); count = read(0, input, 49999); input[count]='\0'; fprintf(out, "-----1234567890df\n"); fprintf(out, "Content-Type: text/html; charset=iso-8859-1\n" "Content-Transfer-Encoding: 8bit\n"); fprintf(out, input); pclose(out); } I would like to known if some of you have faced such a problem! Please let me know and how you did solve it! I am desperatly to fix this problem! Thanks a lot for your time and cooperation, best regards!
BSD is not my choice of OSes but a sig 11 in linux is commonly a memory error, almost always a hardware error. Have you strained this box by doing anything else on it? My best guess would be that hardware is screwing it up, possibly under the strain of the MANY messages you claim. -- Tim ----- Original Message ----- From: "Gustavo Vieira Goncalves Coelho Rios" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 12:21 PM Subject: qmail + freebsd = reboot > Dear gentleman, > > i have just installed qmail in my freebsd box, but after request qmail > to send my message, i got my box reboot. At a first look, the machine is > not supposed to be reboot under a software error, if it does it is an > operating system problem matter. > > FreeBSD is well known for its rock solid performance, but i am really > confused since another server running linux do the job very well. > > This reboot only happens when i send MANY message to a domain outside my > box one, all local messages are delivered very well. My qmail version is > 1.03 > > here goes my uname -a: > > grios@etosha:~$ uname -a > FreeBSD etosha 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT > 2000 root@etosha:/usr/obj/usr/src/sys/ETOSHA i386 > > > All i got in /var/log/messages is (only the part pertinent to qmail) > > Sep 13 17:12:21 etosha /kernel: pid 3197 (qmail-remote), uid 1008: > exited on sig > nal 11 > > > my dmesg is:Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 > root@etosha:/usr/obj/usr/src/sys/ETOSHA > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x634 Stepping = 4 > > Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,M MX > > > real memory = 134217728 (131072K bytes) > avail memory = 127643648 (124652K bytes) > Preloaded elf kernel "kernel" at 0xc030c000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc030c09c. > Preloaded elf module "vesa.ko" at 0xc030c0ec. > grios@etosha:/var/log$ /sbin/dmesg > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 > root@etosha:/usr/obj/usr/src/sys/ETOSHA > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x634 Stepping = 4 > > Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,M MX> > real memory = 134217728 (131072K bytes) > avail memory = 127643648 (124652K bytes) > Preloaded elf kernel "kernel" at 0xc030c000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc030c09c. > Preloaded elf module "vesa.ko" at 0xc030c0ec. > VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc00c6d9d (c0006d9d) > VESA: Diamond Multimedia Systems, Inc. > Pentium Pro MTRR support enabled > apm0: <APM BIOS> on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > npx0: <math processor> on motherboard > npx0: INT 16 interface > pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard > pci0: <PCI bus> on pcib0 > pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 on > pci0 > pci1: <PCI bus> on pcib1 > pci1: <S3 ViRGE GX2 graphics accelerator> at 0.0 irq 11 > isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 > on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 12 > chip1: <Intel 82371AB Power management controller> port 0x5000-0x500f at > device 7.3 on pci0 > ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xe400-0xe4ff mem > 0xe9000000-0xe9000fff irq 11 at device 11.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > isa0: too many dependant configs (8) > isa0: unexpected small tag 14 > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: <System console> on isa0 > sc0: VGA <10 virtual consoles, flags=0x200> > sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 > sio1: type 16550A > sio2 at port 0x3e8-0x3ef irq 4 on isa0 > sio2: type 16550A > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: IEEE1284 device found /NIBBLE/ECP > Probing for PnP devices on ppbus0: > ppbus0: <HEWLETT-PACKARD DESKJET 610C> MLC,PCL,PML > lpt0: <Printer> on ppbus0 > lpt0: Interrupt-driven port > ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 > ed0: address 00:00:21:6c:8f:e0, type NE2000 (16 bit) > sbc0: <Creative SB AWE64> at port 0x220-0x22f,0x330-0x331,0x388-0x38b > irq 5 drq 1,5 on isa0 > sbc0: setting card to irq 5, drq 1, 5 > pcm0: <SB DSP 4.16> on sbc0 > unknown0: <Game> at port 0x200-0x207 on isa0 > unknown1: <WaveTable> at port 0x620-0x623 on isa0 > IP packet filtering initialized, divert enabled, rule-based forwarding > disabled, default to accept, unlimited logging > ad0: 8063MB <QUANTUM FIREBALL SE8.4A> [16383/16/63] at ata0-master using > UDMA33 > afd0: 96MB <IOMEGA ZIP 100 ATAPI Floppy> [96/64/32] at ata1-master using > PIO0 > acd0: CDROM <34X CD-ROM> at ata1-slave using UDMA33 > Mounting root from ufs:/dev/da0s1a > da0 at ahc0 bus 0 target 6 lun 0 > da0: <QUANTUM VIKING II 9.1WSE 5520> Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing > Enabled > da0: 8709MB (17836668 512 byte sectors: 64H 32S/T 8709C) > WARNING: / was not properly dismounted > > > > I am really confused how this error could reboot my box, since i have no > knowledge on freebsd internals. > > > > Everything i did to send message was: > > grios@etosha:~/personal$ ./mail [EMAIL PROTECTED] > <~guest/teste_mail.txt > > > And the source code for mail.c is: > > grios@etosha:~/personal$ more mail.c > #include <stdio.h> > > #define MAIL_BINARY "/usr/bin/mail" > > int > main(int argc, char *argv[]) > { > FILE *out; > char buffer[255], > input[50000]; > int count; > > sprintf(buffer, "%s %64s", MAIL_BINARY, argv[1]); > out = popen(buffer, "w"); > > fprintf(out, "\bContent-Type: > multipart-mixed;\nboundary=\"---1234567890df > \";\n"); > > count = read(0, input, 49999); > input[count]='\0'; > fprintf(out, "-----1234567890df\n"); > fprintf(out, "Content-Type: text/html; charset=iso-8859-1\n" > "Content-Transfer-Encoding: 8bit\n"); > fprintf(out, input); > > pclose(out); > } > > > I would like to known if some of you have faced such a problem! Please > let me know and how you did solve it! I am desperatly to fix this > problem! > > Thanks a lot for your time and cooperation, > best regards! > >
* Gustavo Vieira Goncalves Coelho Rios <[EMAIL PROTECTED]> [000913 15:23] wrote: > Dear gentleman, > > i have just installed qmail in my freebsd box, but after request qmail > to send my message, i got my box reboot. At a first look, the machine is > not supposed to be reboot under a software error, if it does it is an > operating system problem matter. Please see: http://www.freebsd.org/handbook/kerneldebug.html for a way to get us a system traceback. -Alfred
I made a QMAIL-BOX using FreeBSD2.2.8. I have been testing it for over a month and found it working well. It consists of 1(2)Floppy diskettes and use entire HDD as mail spool. Installation to new PC is very easy and takes less than fifteen minutes. First diskette includes FreeBSD and QMAIL-1.03 and pop3d and tcpserver. Second one includes Courier-IMAP. First diskette can work without second one. I f you like to use C-Imap, you shoud use second fd, too. I will use it for a school internet at elementary school , that my kids are attending. I have my home page to introduce and distribute my free binary (http://www.ryuchi.org/~ilovefd). I am thinking of putting 1(2)FD-QMAIL/POP3/C-IMAP on my HP in a few days. Sincerely Y.NISHIMURA
Tim Hunter <[EMAIL PROTECTED]> writes: > BSD is not my choice of OSes but a sig 11 in linux is commonly a memory > error, almost always a hardware error. It's also quite frequently a symptom of an overheated CPU, particularly if it occurs randomly and is difficult to reproduce. If you're overclocking, that's the first place that I'd look. See <http://www.bitwizard.nl/sig11/>. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 that sounds kinda odd, i've been using qmail for almost 4 years now and this is the first time i've heard of such incident. how did you install qmail? Jonel Rienton http://qmail.freebsduser.org sent by qmail-1.03 on a FreeBSD 4.1-STABLE - ----- Original Message ----- From: "Gustavo Vieira Goncalves Coelho Rios" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, September 13, 2000 2:21 PM Subject: qmail + freebsd = reboot | Dear gentleman, | | i have just installed qmail in my freebsd box, but after request | qmail to send my message, i got my box reboot. At a first look, the | machine is not supposed to be reboot under a software error, if it | does it is an operating system problem matter. | | FreeBSD is well known for its rock solid performance, but i am | really confused since another server running linux do the job very | well. | | This reboot only happens when i send MANY message to a domain | outside my box one, all local messages are delivered very well. My | qmail version is 1.03 | | here goes my uname -a: | | grios@etosha:~$ uname -a | FreeBSD etosha 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Sep 10 | 17:59:18 GMT 2000 root@etosha:/usr/obj/usr/src/sys/ETOSHA i386 | | | All i got in /var/log/messages is (only the part pertinent to | qmail) | | Sep 13 17:12:21 etosha /kernel: pid 3197 (qmail-remote), uid 1008: | exited on sig | nal 11 | | | my dmesg is:Copyright (c) 1992-2000 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, | 1994 | The Regents of the University of California. All rights | reserved. | FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 | root@etosha:/usr/obj/usr/src/sys/ETOSHA | Timecounter "i8254" frequency 1193182 Hz | CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) | Origin = "GenuineIntel" Id = 0x634 Stepping = 4 | | Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MC | A,CMOV,MMX | real memory = 134217728 (131072K bytes) | | avail memory = 127643648 (124652K bytes) | Preloaded elf kernel "kernel" at 0xc030c000. | Preloaded userconfig_script "/boot/kernel.conf" at 0xc030c09c. | Preloaded elf module "vesa.ko" at 0xc030c0ec. | grios@etosha:/var/log$ /sbin/dmesg | Copyright (c) 1992-2000 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, | 1994 | The Regents of the University of California. All rights | reserved. | FreeBSD 4.1-STABLE #0: Sun Sep 10 17:59:18 GMT 2000 | root@etosha:/usr/obj/usr/src/sys/ETOSHA | Timecounter "i8254" frequency 1193182 Hz | CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) | Origin = "GenuineIntel" Id = 0x634 Stepping = 4 | | Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MC | A,CMOV,MMX> real memory = 134217728 (131072K bytes) | avail memory = 127643648 (124652K bytes) | Preloaded elf kernel "kernel" at 0xc030c000. | Preloaded userconfig_script "/boot/kernel.conf" at 0xc030c09c. | Preloaded elf module "vesa.ko" at 0xc030c0ec. | VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc00c6d9d | (c0006d9d) VESA: Diamond Multimedia Systems, Inc. | Pentium Pro MTRR support enabled | apm0: <APM BIOS> on motherboard | apm: found APM BIOS v1.2, connected at v1.2 | npx0: <math processor> on motherboard | npx0: INT 16 interface | pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard | pci0: <PCI bus> on pcib0 | pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 | on pci0 | pci1: <PCI bus> on pcib1 | pci1: <S3 ViRGE GX2 graphics accelerator> at 0.0 irq 11 | isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0 | isa0: <ISA bus> on isab0 | atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at | device 7.1 on pci0 | ata0: at 0x1f0 irq 14 on atapci0 | ata1: at 0x170 irq 15 on atapci0 | pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 12 | chip1: <Intel 82371AB Power management controller> port | 0x5000-0x500f at device 7.3 on pci0 | ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xe400-0xe4ff mem | 0xe9000000-0xe9000fff irq 11 at device 11.0 on pci0 | ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs | isa0: too many dependant configs (8) | isa0: unexpected small tag 14 | atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 | atkbd0: <AT Keyboard> irq 1 on atkbdc0 | vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff | on isa0 | sc0: <System console> on isa0 | sc0: VGA <10 virtual consoles, flags=0x200> | sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 | sio1: type 16550A | sio2 at port 0x3e8-0x3ef irq 4 on isa0 | sio2: type 16550A | ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 | ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode | ppbus0: IEEE1284 device found /NIBBLE/ECP | Probing for PnP devices on ppbus0: | ppbus0: <HEWLETT-PACKARD DESKJET 610C> MLC,PCL,PML | lpt0: <Printer> on ppbus0 | lpt0: Interrupt-driven port | ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 | ed0: address 00:00:21:6c:8f:e0, type NE2000 (16 bit) | sbc0: <Creative SB AWE64> at port | 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 | sbc0: setting card to irq 5, drq 1, 5 | pcm0: <SB DSP 4.16> on sbc0 | unknown0: <Game> at port 0x200-0x207 on isa0 | unknown1: <WaveTable> at port 0x620-0x623 on isa0 | IP packet filtering initialized, divert enabled, rule-based | forwarding disabled, default to accept, unlimited logging | ad0: 8063MB <QUANTUM FIREBALL SE8.4A> [16383/16/63] at ata0-master | using UDMA33 | afd0: 96MB <IOMEGA ZIP 100 ATAPI Floppy> [96/64/32] at ata1-master | using PIO0 | acd0: CDROM <34X CD-ROM> at ata1-slave using UDMA33 | Mounting root from ufs:/dev/da0s1a | da0 at ahc0 bus 0 target 6 lun 0 | da0: <QUANTUM VIKING II 9.1WSE 5520> Fixed Direct Access SCSI-2 | device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), | Tagged Queueing Enabled | da0: 8709MB (17836668 512 byte sectors: 64H 32S/T 8709C) | WARNING: / was not properly dismounted | | | | I am really confused how this error could reboot my box, since i | have no knowledge on freebsd internals. | | | | Everything i did to send message was: | | grios@etosha:~/personal$ ./mail [EMAIL PROTECTED] | <~guest/teste_mail.txt | | | And the source code for mail.c is: | | grios@etosha:~/personal$ more mail.c | #include <stdio.h> | | #define MAIL_BINARY "/usr/bin/mail" | | int | main(int argc, char *argv[]) | { | FILE *out; | char buffer[255], | input[50000]; | int count; | | sprintf(buffer, "%s %64s", MAIL_BINARY, argv[1]); | out = popen(buffer, "w"); | | fprintf(out, "\bContent-Type: | multipart-mixed;\nboundary=\"---1234567890df | \";\n"); | | count = read(0, input, 49999); | input[count]='\0'; | fprintf(out, "-----1234567890df\n"); | fprintf(out, "Content-Type: text/html; | charset=iso-8859-1\n" | "Content-Transfer-Encoding: 8bit\n"); | fprintf(out, input); | | pclose(out); | } | | | I would like to known if some of you have faced such a problem! | Please let me know and how you did solve it! I am desperatly to fix | this | problem! | | Thanks a lot for your time and cooperation, | best regards! | | | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with "unsubscribe freebsd-stable" in the body of the message -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQA/AwUBOcAyHqQ0pAI9Fl/WEQLjgwCcC+XmMAK8WW2Da9VNIbK5BtJ0+o0AoMdo zLVyBBfAKsKL2BwSACbfJVkv =g6FT -----END PGP SIGNATURE-----
> i have just installed qmail in my freebsd box, but after request qmail > to send my message, i got my box reboot. At a first look, the machine is > not supposed to be reboot under a software error, if it does it is an > operating system problem matter. Well, it's still not exactly clear _why_ your box rebooted and it won't be clear to anyone not physically with you in Brazil until we get some sort of panic message or a kernel traceback or something which indicates just where the problem occurred. Such issues are also frequent indications that something is not quite right with the hardware, and without more data it's really hard to know just what exactly is going on. - Jordan
Hi, I'm not familiar with BSD's either since I never worked with them, but I also suspected that maybe it is a CPU over-heat. In my case, I was over-clocking a little bit but it was a CYRIX 233 ( what'd you expect ;) ) and it mysteriously kept going down. Of course, I cant interpret oops logs so I left the situation alone until I found a s*it load of dust clogging up the CPU fan and heat sink, bringing it almost to a halt. Man was that baby burnin' ;) Cleaned it up, set jumpers back to default and all is well now. Since I'm on a maintenance-talk spree :) --- Sometimes cheap RAM is known to be buggy. Also, pluging/unpluging of cards/cables/ram etc helps since corrosion builds up between the contacts over a period of time and loses some conductivity (living here in Japan with all this moist is a real killer). cheers, jamie ps maybe its an unknown virus that eats the cpu waffers (just kidding...) > > BSD is not my choice of OSes but a sig 11 in linux is commonly > > a memory error, almost always a hardware error. > > It's also quite frequently a symptom of an overheated CPU, par- > ticularly if it occurs randomly and is difficult to reproduce. > If overclocking, you're that's the first place that I'd look. #---------#---------#---------#---------#---------#---------#---------# -- If somebody can help create a search engine for my room, I will call them a Saint... GUI == Graphical User Interference
http://www.wahoo-band.com
http://wahoo.eu.org
Mail : [EMAIL PROTECTED]-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Thus spake Dejan Markic ([EMAIL PROTECTED]): > So ... I have put virtual domain to virtualdomains file: > > my.virtual.domain.com:user That means, that a mail to [EMAIL PROTECTED] will be sent locally to user-my.virtual.domain.com-foo Please note the complete virtualdomain in the forwarded address. > I touch file named .qmail-info (i don't write anything in this file). This doesn�t fit. For the domain above, you have to touch .qmail-my:virtual:domain:com-info > Please help, I am in hurry... Stay calm. Relax. Enjoy beauty. cheers, oec
Dear gentleman, do anyone here already faced qmail rebooting your box? I am running freebsd 4.1Stable and qmail 1-03 and after sending too many message to domains outside locals i got my box reboot and in /var/log/messages a line telling that qmail-remote received sigsev signal! *PLEASE* let me know if you have ever faced that and how you did solved it! Thanks a LOT for your time and cooperation, best regards!
Quoting Gustavo Vieira Goncalves Coelho Rios ([EMAIL PROTECTED]): > do anyone here already faced qmail rebooting your box? > I am running freebsd 4.1Stable and qmail 1-03 and after sending too many > message to domains outside locals i got my box reboot and in > /var/log/messages a line telling that qmail-remote received sigsev > signal! Userland programs not running as root can't reboot your machine. I should say, they should not be able to. If qmail-remote is segfaulting and your machine is rebooting I would look into the hardware, i.e. proper cooling, or even try replacing the RAM. Bad RAM can cause programs to segfault, and other very undesirable behavior. Aaron
Problem 1: Various qmail components check the return code of processes they spawn, and use that value to decide whether the processes completed successfully, or whether the failure was permanent or transient (zero return code is always interpreted as a success, termination by a signal is always interpreted as a transient failure). source (executed program) return code interpretation qmail.c (qmail-queue) 11..40,115 permanent f. other transient f. qmail-rspawn.c (qmail-remote) 111 transient f. other permanent f. (!!!) qmail-lspawn.c (qmail-local, QLX_EXECHARD permanent f. qmail-getpw) other QLX_* transient f. 111,71,74,75 transient f. other permanent f. (!!!) qmail-local.c (|command) 100,64,65,70, permanent f. 76,77,78,112 99 special other transient f. You can see that qmail-rspawn.c and qmail-lspawn.c interpret all unknown errors as permanent. Unfortunately, many existing dynamic linker implementations (see appendix A) call _exit() with some specific return code when the dynamic linking fails (e.g. due to a momentary shortage of free resources). qmail-[rl]spawn would interpret it as a permanent failure and bounce the mail. If your karma is bad enough, and qmail-queue keeps working even when qmail-remote and qmail-local keep failing in that "permanent" way, the bounce will turn into a double-bounce, and the double-bounce will be bounced into oblivion. In other words, qmail will discard the mail for something that looks a lot like a "frivolous reason". I leave it up to you to decide how the blame should be distributed between qmail and the dynamic linker. Surprisingly, qmail.c and qmail-local.c are much more careful: everything but the explicitly named values is interpreted as a transient failure (this also means a mistyped command after | in .qmail will probably not cause bounces, see appendices B and C.) (Well, qmail-queue's return codes (interpreted in qmail.c) indicating a permanent failure collide with the codes used by the old Linux ld.so but this is not very important because libc5 is really obsolete.) Problem 2: I think someone have already mentioned it: qmail inteprets execve() failure as a permanent delivery failure in many situations when it makes no sense. source (execute program) interpretation of execve() failure qmail.c (qmail-queue) transient (_exit(120)) qmail-rspawn.c (qmail-remote) determined by error_temp(errno) qmail-lspawn.c (qmail-local) determined by error_temp(errno) qmail-lspawn.c (qmail-getpw) transient (_exit(QLX_EXECPW)) qmail-local (|command) transient (_exit(111)) error_temp(errno) checks whether the error is of transient nature (i.e. it is going to disappear soon without an external intervention). But is a missing (ENOENT) or corrupted (ENOEXEC) file, or a file with incorrect permissions (EACCES) a good reason to start bouncing mails? (With a "very descriptive" error message saying something like "Unable to run qmail-remote".) Appendix A: dynamic linker failure: Linux ld-linux.so 1.9.9 (libc5 ld.so) _exit(N) for 1 <= N <= cca. 20 Linux glibc 2.0.7, 2.1.3 ld-linux.so.2 _exit(127) FreeBSD 3.4-STABLE ld-elf.so.1 _exit(1) Solaris 2.5, 2.6 ld.so.1 kill(getpid(), SIGKILL) HP-UX 10.20 dld.sl ??? _exit(12) (*) (*) dld.sl(5) says the dynamic linker will abort (SIGABRT) when it encounters a fatal error but the only failure I was able to induce experimentally lead to _exit(12) Appendix B: sh -c '(' (syntax error) GNU bash 1.14.7, 2.01.1 _exit(2) FreeBSD 3.4-STABLE sh _exit(2) Solaris 2.6 sh _exit(2) HP-UX 10.20 sh _exit(2) Appendix C: sh -c blah (nonexistent command) GNU bash 1.14.7, 2.01.1 _exit(127) FreeBSD 3.4-STABLE sh _exit(127) Solaris 2.6 sh _exit(1) HP-UX 10.20 sh _exit(1) --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "Resistance is futile. Open your source code and prepare for assimilation."
On Thu, Sep 14, 2000 at 12:01:41PM +1000, Ramzi S. Abdallah wrote: > What patches I needs to have a secure and stable installation of qmail. I am > trying to install qmail for the first time but I am a bit confused as there > is a lot of patches and fixes written by different contributors. Why aren't > all those patches included in the source if they are useful for the day to > day operation of qmail :) qmail is secure and stable without any patches. Unless you have special needs that require patching, you should be able to run qmail just fine right out of the box. Chris
Ramzi S Abdallah <[EMAIL PROTECTED]> writes: > What patches I needs to have a secure and stable installation of > qmail. None. I've been running qmail for years now and I've yet to install a single patch. I use qmail 1.03 straight out of the box. You need patches if you need particular features that stock qmail doesn't provide, such as LDAP support or authenticated SMTP, but for straightforward mail service you don't need any of them. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Hi, folks. I have an mail account, which makes a forward to another account, through a .qmail file. How I can add a phrase to the incoming mail to know that it is a forward? Thanhs!
I encountered a weird problem today with a <shudder> majordomo list that created a nasty mail loop and dumped over a thousand messages into our remote queue. And yes, I will be converting the list from majordomo to ezmlm tomorrow. I ended up creating a quick script that dug through the output of qmail-qread and cut out the message numbers, than ran that through a find command that removed all of those messages from the queue. It appears to have worked. However, my question is this: Was there a better way to remove messages FROM a specific sender? I've seen several discussions on removing messages TO a specific user or domain... Thanks, Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
Hello all, My openldap's replica works fine with each one user insert operation. But i create simple script for just 10 user add operation and executed it on the master, replica lost 2 or 3 entry. Do you have any idea ? or openldap's replica don't have reliability ? I don't understand, please mail to me. Thanks, Michael.
Hi, I was wondering if somebody could help me out with the syntax to multilog. Please bare with me and my dumb question since I am not the one at "production level" yet with qmail...and heck, this may not be a multilog thing at all. In my /var/qmail/rc I have the following: (snipped from lwq - great doc!) #!/bin/sh exec env - $PATH="/var/qmail/bin":$PATH \ qmail-start '|preline procmail' splogger qmail Is there a way to change the above splogger to multilog (or something equivalent) and stop logging to syslog? Can you show me an example syntax (if this is possible)? I read the docs but am still confused. I am still experimenting with vsm and procmail so I have not migrated to Maildir yet, but I want to stop using syslog any further. My set up is on a LINUX and almost 100% with lwq. (+local-time and DNS patch). qmail-smtpd is already using multilog at /var/log/qmail. I guess what I wanted to say was that all remote mailing is logged via multilog, but local mail is through syslog so I wanted any qmail mailing to log via multilog whether it be through procmail or Maildir style. I hope I'm making sense. Am I? ;) Pointers, URLS, man(n)? Thanks in advance. jamie #---------#---------#---------#---------#---------#---------#---------# -- If somebody can help create a search engine for my room, I will call them a Saint... GUI == Graphical User Interference
On Thu, Sep 14, 2000 at 01:58:43PM +0900, James T. Perry wrote: > > Hi, > > I was wondering if somebody could help me out with the syntax > to multilog. > Please bare with me and my dumb question since I am not the > one at "production level" yet with qmail...and heck, this may > not be a multilog thing at all. > > In my /var/qmail/rc I have the following: > (snipped from lwq - great doc!) > > #!/bin/sh > exec env - $PATH="/var/qmail/bin":$PATH \ > qmail-start '|preline procmail' splogger qmail > > Is there a way to change the above splogger to multilog > (or something equivalent) and stop logging to syslog? Sure. 1. Make a log directory for all the goodies that multilog likes, say, /var/log/qmail/send mkdir /var/log/qmail/send 2. Make sure this directory is owned by qmaill chown qmaill /var/log/qmail/send chmod u=rwx,og=rx /var/log/qmail/send (Note that I don't see anywhere in the docs where it states that logger is started with uid qmaill, but it is, and it makes sense.) 3. Change your startup to something like: exec env - $PATH="/var/qmail/bin":$PATH \ qmail-start '|preline procmail' /usr/local/bin/multilog t /var/log/qmail/send 4. Restart qmail - perhaps with svc -t /service/qmail > qmail-smtpd is already using multilog at /var/log/qmail. Ahh. In this case, you will need to separate your multilogs, perhaps /var/log/qmail/send and /var/log/qmail/smtpd FAQ 7.7 makes an ancient reference to a similar process. It's worth reading, if only for historical interest. Regards.
Hi all ! I find this error while delivering mail to [EMAIL PROTECTED] As this error persist for several days and looking for MX and A, CNAME records with nslookup was succesfull I try to look at qmail-remote under GDB. And find out that in function "resolve" in dns.c A buffer of PAKETSZ bytes (defined in <arpa/nameser.h> as 512) was used. And the real response length was more than 1100 !!! That's why qmail-remote was unable to make CNAME lookup. I have redefined PACKETSZ in "dns.h" to 2048 and after that all my mail to mail.ru was delivered :-)) Now I don't know what shall I do because I don't think that my solution is "perfect" one. May be this should be reported as "BUG" in qmail ? Or it's a bug somewhere else (I mean the author of <arpa/nameser.h>) ?
Hello all, I wnat to know more detail howto mini-qmail, where i can find it ? Thanks, Michael.
* Michael Y. Kim <[EMAIL PROTECTED]> [000914 04:19]: > I wnat to know more detail howto mini-qmail, where i can find it ? Does this help: http://cr.yp.to/qmail/mini.html http://www.google.com/search?client=googlet&q=mini-qmail
> On 13-Sep-2000, Jerry Hsieh wrote: > > " The mail server responded: sorry, that domain isn't in my list of allowed > > rcphosts. Please check the message receipients and try again" > > > > If I add the xyz.com in the rcphosts and it works. My question is how can I > > edit this file (by addind all the domain? Noooooo) or there is better way I > > can do about it? Thanks for your time. (I say this seriously - not to belittle the guy asking the FAQ) I think I'm going to start working on a listbot that attempts to automatically respond (off list) to FAQs. I think I could do a fuzzy regex search on some common qmail error messages (and their mispellings) and send a canned response - it will probably be very simplistic, as I have lots of other irons in my fire... Has anyone started such a project and let it fallow, who might like some help? Any other Pythoneers out there interested in colaborating? Also, is there a downside to this that I just can't see? Am I asking for trouble by having a bot listen in on this list? Eric
Hi, Who is the list owner for this list, please? Our site is seeing very heavy DNS traffic due to (without permission!!) our DNS being shown on the list of DNS servers for the 'idea.co.uk' domain. Apparently idea.co.uk is no longer in use, and if there happen to be any idea.co.uk (or bad.idea.co.uk, which is another address we're seeing) on this list, I would very much appreciate it if those addresses can be removed from the list as soon as possible. I have asked UUNET Pipex to update the idea.co.uk domain record so that we're taken off the list, but in the mean time it would be useful if those users could be removed from the qmail list. It is possible that this traffic is being used to provide cover for an (unsuccesful, but bandwidth eating) DOS attack on our DNS, so any help in sorting this out quickly would be much appreciated. -- Sarah Thompson CEO, TradeWorks Ltd. PS: We use qmail ourselves, and think it is superb.
> hadn't got around to complaining to them yet. it appears that they > don't care anyway. pitty i may just have to block them too. The world is full of such sites. For the case of "gone users still receiving mail" the badrcptto-patch is very useful. Regards, Frank
