[Exim] Truncated log entry...unfortunately

Top Page
Delete this message
Reply to this message
Author: John W Baxter
Date:  
To: exim-users
Subject: [Exim] Truncated log entry...unfortunately
Exim 4.10, Red Hat 7.3 I did try the FAQ, and list archive unsuccessfully,
but may have missed something.

First, I'm not very good at writing Exim conditionals...I often get my
bearings all balled up when doing so.

Second, I'm trying to adjust the Received: header (specifically the for xxx
phrase).

And I've failed...Exim is logging the failure. Unfortunately, the value of
received_header_text is a large string by default, and I've made it larger
(more sources of xxx in the for xxx phrase). It is large enough that Exim
is truncating the entry at roughly the end of the text I know, but before
Exim's commentary as to what is wrong.

I could
  find the truncation in the Exim source and "fix" it temporarily
  leave the error out of the text of the received_header_text option
  remove some other clauses temporarily from the received header
      to shorten the log entry.  I'll probably do this followed by leaving
the error out.
      This is a standby server, so that course is reasonable.
  learn to write Exim conditional expansions right the first time (I
managed one today)


I haven't found options or command line flags to change the truncation
point...I agree there needs to be a truncation point.

Potential wish list item (lowish but non-zero priority):  one or more of
   a.  shorten selected log entries by eliding the middle rather than
chopping the end
   b.  in this particular entry, put the cause commentary before the text
of the failing expansion
        There may be other candidates for this sort of treatment.
   c.  provide a main configuration option (which could then be set by
macro and controlled by -D)
       for log entry length limit.


--John

--
John Baxter   jwblist@???      Port Ludlow, WA, USA