On Wed, Apr 24, 2002 at 08:39:49PM -0600, Oscar Bonilla wrote: > On Thu, Apr 25, 2002 at 01:55:28AM +0000, Dan Melomedman wrote: > > Post your configs. > > Here they are... (see more comments at the end) > <BIG SNIP> > ----- > > I use concurrencyincomming when I start qmail-smtpd to limit the > number of connections. > > I use defaultdelivery in /var/qmail/rc as an argument to qmail-start > (taken from lifewithqmail/ldap) > > I tried to get more info by adding my own debug messages. Since the last > log line I get for local deliveries that fail is > > delivery 329: log: LOGLEVEL_set_to_63/ > > I tried adding this to the spawn function in qmail-lspawn.c > > log(16, "obdebug: in spawn"); > > sig_hangupdefault(); /* clear the hup sig handler for the child */ > > log(16, "obdebug: done sighup"); > > > Unfortunately the last obdebug log I see for either succesful or > unsuccesfule deliveries is > > delivery 329: log: obdebug:_in_spawn > > For instance, this is a successful delivery: > > starting delivery 329: msg 3761672 to local [EMAIL PROTECTED] > status: local 22/120 remote 1/120 > delivery 329: log: LOGLEVEL_set_to_63/ > delivery 329: log: obdebug:_in_spawn > delivery 329: log: >ldapfilter:_'(|([EMAIL PROTECTED])([EMAIL PROTECTED]))'/ > delivery 329: log: >found:_user='obonilla'_uid=1020_gid=444_homedir='/home/profesor/obonilla'_mms='(null_pointer)'_host='hermes.galileo.edu'_status=0/ > delivery 329: log: LDAP_lookup_succeeded/ > delivery 329: success: did_1+0+0/ > > this is an unsuccesful one: > > starting delivery 3: msg 3761741 to local @hermes.galileo.edu > status: local 3/120 remote 0/120 > delivery 3: log: LOGLEVEL_set_to_63/ > > there's no more info about delivery 3 in the logs. Also notice that > the email address is @hermes.galileo.edu. I don't know where this > comes from... the message number 3761741 reads: >
Strange is that a lot of debug/log output is missing. How often do you have problems? Some ideas: Try to run a version without DEBUG support (the log support could probably interfere the communication with the main lspawn process and/or qmail-send. If you have unsucessful deliveries are then multiple qmail-lspwan running or have those child qmail-lspawn crashed? Does it stop on random messages or are always the same messages causing problems. If one of the program is crashing could you try to get a core dump and a backtrace? > hermes ~/tmp # qmHandle -v3761741 > > -------------- > MESSAGE NUMBER 3761741 > -------------- > Received: (qmail 72269 invoked by uid 80); 20 Apr 2002 20:50:33 -0000 > Received: from 192.168.2.95 ( [192.168.2.95]) > as user [EMAIL PROTECTED] by mail.galileo.edu with HTTP; > Sat, 20 Apr 2002 14:50:33 -0600 > Message-ID: <[EMAIL PROTECTED]> > Date: Sat, 20 Apr 2002 14:50:33 -0600 > From: [EMAIL PROTECTED] > To: [email protected] > Cc: [EMAIL PROTECTED] > Subject: XXXXXXX > MIME-Version: 1.0 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 8bit > User-Agent: Internet Messaging Program (IMP) 3.0 / FreeBSD-4.4 > X-Originating-IP: 192.168.2.95 > > <BODY OF EMAIL DELETED> > Have you seen the strange to address? It would be intresting to know the enveloppe of the message (queue/local/*/3761741 and queue/info/*/3761741). I will try to set up a test machine to trigger the problem (there was already someone complaining about strange things in qmail-lspawn). -- :wq Claudio
