On Friday 25 August 2006 14:17, Claudio Jeker wrote with regard to - Re: Big request for some assistance : > On Fri, Aug 25, 2006 at 12:37:30PM +0200, Scott Ryan wrote: > > On Friday 25 August 2006 11:30, Scott Ryan wrote with regard to - Re: Big > > > > request for some assistance : > > > Just to add to this: When messages are bounced, I get a return code > > > from bouncesaying as 100. But when they are not bounced, the return > > > code is 4294967295 > > > > Does bouncesaying log anywhere? Does it have any memory limits enforced? > > (Eg. Does it read ~controls/databytes). > > Is there a way that I can patch bouncesaying to output some debugging > > messages? I can't see anywhere in the code that would give an exit code > > of anything other than 0,111 or 100. Yet maildrop is telling me that the > > exit code was 4294967295. What could this number be? > > 4294967295 == 0xffffffff == (unsigned int) -1
Brilliant. I didn't think of checking this. > > > I am really at my wits end with this issue and if anyone could shed some > > light on what bouncesaying actually does, it would be a massive help. > > This is not a problem of bouncesaying. IMO this is a maildrop issue/bug. > I guess maildrop does not correctly handle the fact that bouncesaying is > not reading a single byte form stdin but that's just wild guessing as I > never used maildrop nor have I looked at it. I will try the courier-maildrop mailing list. Many thanks for your help. -- Regards, Scott Ryan Telkom Internet
