Yes, I'm using centos 4.4, toaster versions are as below (They were current when the install took place):
rwxr-xr-x 2 root root 4096 Sep 6 14:38 . drwxr-xr-x 4 root root 4096 Sep 1 16:38 .. -rw-r--r-- 1 root root 17662 Sep 1 19:52 autorespond-toaster-2.0.4-1.3.1.src.rpm -rw-r--r-- 1 root root 7513273 Sep 1 19:52 clamav-toaster-0.88.4-1.3.3.src.rpm -rw-r--r-- 1 root root 935 Sep 1 19:52 cnt40-deps.sh -rw-r--r-- 1 root root 6219 Sep 6 15:02 cnt40-install-script.sh -rw-r--r-- 1 root root 530 Sep 1 19:52 cnt40-perl.sh -rw-r--r-- 1 root root 2050 Sep 1 19:52 cnt40-svcs.sh -rw-r--r-- 1 root root 27359 Sep 1 19:52 control-panel-toaster-0.5-1.3.1.src.rpm -rw-r--r-- 1 root root 2014194 Sep 1 19:52 courier-authlib-toaster-0.58-1.3.1.src.rpm -rw-r--r-- 1 root root 3234935 Sep 1 19:52 courier-imap-toaster-4.1.1-1.3.2.src.rpm -rw-r--r-- 1 root root 663 Sep 1 19:52 current-download-script.sh -rw-r--r-- 1 root root 51327 Sep 1 19:52 daemontools-toaster-0.76-1.3.1.src.rpm -rw-r--r-- 1 root root 161178 Sep 1 19:52 djbdns-1.05-1.0.2.src.rpm -rw-r--r-- 1 root root 509353 Sep 1 19:52 ezmlm-toaster-0.53.324-1.3.1.src.rpm -rw-r--r-- 1 root root 12154 Sep 1 19:52 EZ-QmailToaster-CentOS-4.3.txt -rw-r--r-- 1 root root 3472 Sep 1 19:52 firewall.sh -rw-r--r-- 1 root root 87769 Sep 1 19:52 isoqlog-toaster-2.1-1.3.1.src.rpm -rw-r--r-- 1 root root 42568 Sep 1 19:52 libdomainkeys-toaster-0.68-1.3.1.src.rpm -rw-r--r-- 1 root root 2146132 Sep 1 19:52 maildrop-toaster-2.0.2-1.3.1.src.rpm -rw-r--r-- 1 root root 2434312 Sep 1 19:52 qmailadmin-toaster-1.2.9-1.3.1.src.rpm -rw-r--r-- 1 root root 23360 Sep 1 19:52 qmailmrtg-toaster-4.2-1.3.1.src.rpm -rw-r--r-- 1 root root 295833 Sep 1 19:52 qmail-toaster-1.03-1.3.5.src.rpm -rw-r--r-- 1 root root 127951 Sep 1 19:52 ripmime-toaster-1.4.0.6-1.3.1.src.rpm -rw-r--r-- 1 root root 171099 Sep 1 19:52 simscan-toaster-1.2-1.3.1.src.rpm -rw-r--r-- 1 root root 991780 Sep 1 19:52 spamassassin-toaster-3.1.4-1.3.2.src.rpm -rw-r--r-- 1 root root 564115 Sep 1 19:52 squirrelmail-toaster-1.4.8-1.3.3.src.rpm -rw-r--r-- 1 root root 68526 Sep 1 19:52 ucspi-tcp-toaster-0.88-1.3.1.src.rpm -rw-r--r-- 1 root root 401609 Sep 1 19:52 vpopmail-toaster-5.4.13-1.3.2.src.rpm -rw-r--r-- 1 root root 94393 Sep 1 19:52 vqadmin-toaster-2.3.4-1.3.2.src.rpm -rw-r--r-- 1 root root 434686 Sep 1 19:52 zlib-1.2.3-1.0.3.src.rpm Chris Godwin Linux/Unix Consultant Network Logistic, Inc. Get help at http://www.networklogistic.com/help -----Original Message----- From: Eric "Shubes" [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 04, 2006 11:18 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Status 11 SIGSEGV This is indeed strange, Chris. Is this a fresh CentOS 4.4 install? Fresh toaster (what versions)? Is the postfix machine on a remote domain (from the toaster's viewpoint)? Chris Godwin wrote: > I don't think that's the case because I'm not getting it now that all > mail comes from the my postfix machine. Keep in mind that the postfix > machine IS NOT given any special tcp.smtp rules. > > What I want to know is how to disable chkuser (I've tried all the > documented methods and it doesn't disable it) I probably messed > something up. What specifically have you tried? I don't know of a way to change chkuser configuration without rebuilding qmail-toaster. In any case, I doubt that's the problem, as mail is flowing from your postfix server. > I also want to know what the BADMIMETYPE and BADLOADERTYPE directives in > tcp.smtp control, or what do they do? I see Peter has answered this. I might add that you can also comment out the entries in the corresponding /var/qmail/control files, then rebuild the cdb's (# qmailctl cdb). > There is something in qmail toaster, but isn't in qmailrocks or lifewith > qmail, that is causeing this. Unpatched qmail works... thus I believe it > is an addon... I just need to disable each until I can find which patch > is doing this. Have you tried using recordio to log the smtp sessions? That might tell you more precisely when/where in the smtp session it's hitting the SEGV. To use recordio with smtp, change /var/qmail/supervise/smtp/run by adding recordio to the exec statement: exec /usr/bin/softlimit -m 12000000 \ /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \ /usr/bin/recordio \ $RBLSMTPD $BLACKLIST $SMTPD $VCHKPW /bin/true 2>&1 (note addition of next to last line) Stop and start qmail, and you'll see the smtp session detail in /var/log/qmail/smtpd/current. Note, it'll generate a *lot* of log content, so you'll want to remove it as soon as you get a sampling. HTH Also, I'm wondering if this could possibly be DNS related. I don't see how. Just wondering. > Chris Godwin > Linux/Unix Consultant > Network Logistic, Inc. > Get help at http://www.networklogistic.com/help > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 04, 2006 10:34 AM > To: qmailtoaster-list@qmailtoaster.com > Subject: RE: [qmailtoaster] Status 11 SIGSEGV > > >> In that configuration I do not see the signal 11. This leads me to >> believe that it isn't an issue with the content of the message killing >> qmail-smtpd, but rather the source in which it is coming from. Has >> anyone seen this or know about it? > > Can't say I've seen this exact same problem, but IIRC (and this may not > directly apply here) if we're talking about a signal 11 segmentation > fault > on a PC platform, it's at least possible that it could be symptomatic of > a > hardware issue (bad RAM, bad cache RAM, motherboard issue). > > --Duncan > > -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
