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.
I also want to know what the BADMIMETYPE and BADLOADERTYPE directives in
tcp.smtp control, or what do they do?

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.

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


---------------------------------------------------------------------
     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]

Reply via email to