Re: [exim] Failed to read delivery status

On Thu, Sep 25, 2008 at 4:53 PM, Chris Zimmerman
<zimmermanc@???>wrote:

>
>
> On Thu, Sep 25, 2008 at 4:17 PM, Phil Pennock <exim-users@???>wrote:
>
>> On 2008-09-25 at 12:32 -0400, Chris Zimmerman wrote:
>> > I was able to find the actual appendfile transport. I apologize, but I'm
>> not
>> > sure how to read it. Not sure if this is a failure or not. This is
>> snippet
>> > of the end of it. It looks to deliver the mail. And it does, but I'm not
>> > sure why it's failing to respond accordingly back to the process that
>> > started it.
>>
>> So it delivers the mail fine, but then doesn't report okay, so when
>> things succeed later the recipient receives a second copy?
>>
>> I see you're using shadow transports for RIM notification. Can you show
>> that configuration too, please?
>>
>> At the moment, based on the information available I will be reviewing
>> the Exim code concerning the shadow transports and how that interacts
>> with alarms. I'll try to look into this tonight.
>>
>> On the bright side, if the mail is getting delivered first time then
>> that explains why you haven't been inundated with user complaints. :)
>>
>> Regards,
>> -Phil
>>
>
>
> Yeah, I was reading some posts from 2004 about sigalarm and calls and well
> it was a bit over my head, I really don't know why it's not responding to
> the sigalarm appropriately instead of dying. Would there be anything as well
> in the debug log for this? I'm looking
>
>
> rim_bis_notifier_virtual_user:
> driver = pipe
> headers_only
> command = /usr/local/cpanel/bin/rim_bis_notifier "${local_part}@
> ${domain}"
> user = "${lookup{$domain}lsearch* {/etc/userdomains}{$value}}"
> group = ${extract{3}{:}{${lookup{${lookup{$domain}lsearch*
> {/etc/userdomains}{$value}}}lsearch{/etc/passwd}{$value}}}}
> log_output = true
> current_directory = "/tmp"
> return_fail_output = true
> return_path_add = false
>



Has anyone any thoughts on this at all? I'm not sure where to proceed.