[prev in list] [next in list] [prev in thread] [next in thread] 

List:       exim-users
Subject:    Re: [exim] logging lmtp delivery
From:       Ian Eiloart <iane () sussex ! ac ! uk>
Date:       2009-01-28 13:05:08
Message-ID: 57B570EEF43AA9E925DDD622 () lewes ! staff ! uscs ! susx ! ac ! uk
[Download RAW message or body]



--On 28 January 2009 19:20:37 +0800 W B Hacker <wbh@conducive.org> wrote:

> Ian Eiloart wrote:
>>
>> --On 28 January 2009 01:03:16 +0800 W B Hacker <wbh@conducive.org> wrote:
>>
>>> And/or... Exim believes that any logging w/r that socket is syslog's
>>> job, not Exim's?
>>
>> Well, it's a cyrus lmtpproxyd. The deliveries are logged on the backend.
>> Not even on the same machine. So, if I'm investigating a problem with a
>> message, then I have to check files on two machines. :(
>
> Not unique - I get around similar challengs with side-by-side SSH
> instances on a wide screen ...

Yes, well I can do the same, but I'm losing a lot of convenience for no 
good reason.

It would be much easier to switch back to delivery using the LMTP option of 
the SMTP transport. I've been using that for some time now, and there's no 
problem with logging.

What I'm looking for here is confirmation that this is a bug worth 
reporting, or a configuration fix if there is one.


> But if it is a frequent need, I'd suggest moving BOTH to syslogd's
> responsibility, then using rsyslog or such to copy one or the other onto
> the opposite box - or a third box.
>
> Contenating into the same file would be more work (probable format
> diff?) and possibly even counterproductive for different daemons, but
> once on the same box wtail or multitail might help.
>
> Bill



-- 
Ian Eiloart
IT Services, University of Sussex
x3148

-- 
## List details at http://lists.exim.org/mailman/listinfo/exim-users 
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[prev in list] [next in list] [prev in thread] [next in thread]