On Jun 28, 2000 Jonathan Haynes <J.Haynes@???> wrote:
> On Wed, 28 Jun 2000 15:22:10 +0100 (BST) Jeffrey Goldberg
> <jeffrey+lists@???> wrote:
> >
> > This problem is not entirely unfamiliar to me.
>
> I didn't realise that we had had it before
Yeah. I'd even reported it to the list.
> > But are you getting it for
> > "only one address" as you say, or for only one value of "xxxxx"?.
> >
>
> Not quite sure what difference you mean by this but
What I meant was that we don't know what conditions are triggering it.
That is, mail to xxxxx works fine, and that it might be mail to yyyyyy
that is triggering these messages.
> > I was thinking of modifying the source
> > where that message is logged to get it to log more information (ID of
> > message, name of file it is trying to read, etc). As you know, this was
> > something that I never got around to.
> >
>
> I had a nasty feeling that might have been the answer - I don't rate my
> C programming highly enough for this :)
I really wish I could help out. But I have a great deal of other things
to do. The few times I've poked into the exim code, it is very clean,
readable and maintainable. It really is just finding out which variables
contain pointers to the strings you need. I know that you know
printf. Look at other examples of calls to the logwrite function. The
only think you need to be careful of is references in NULL pointer, so the
construct
printf("...%s...",
...,
var ? var : "null"
...
if there is a chance of var being NULL at that point.
Of course it won't be printf but whatever the logwrite function is.
-j
--
Jeffrey Goldberg
Note: I am moving and changing many addresses, please see
http://www.goldmark.org/jeff/contact.html
Relativism is the triumph of convention over truth, authority over justice
