> Eric Bullen wrote:
>
>>>What was it supposed to yield? How does your user_list.txt look? Is it
>>>
>>>key1: value1?
>>>key2: value2
>>>or just
>>>key1
>>>key2
>>>?
>>
>>
>> It is:
>>
>> key1\n
>> key2\n
>> etc.
>
> So you have no value that could be yielded. And, this is not the way
> lsearch is supposed to be used ...
Then the documentation needs to be corrected. Here's the exerpt:
"lsearch: The given file is a text file that is searched linearly for a
line beginning with the search key, terminated by a colon or white space
or the end of the line."
My keys are terminated with a newline.
>
>> I have checked to make sure the keys are in the user_list.txt file, and
>> they are there...(otherwise, it would *always* return the 550 error
>> code).
>>
>> Also, here's a telnet session to the exim daemon (while running as 'exim
>> -bd -d -oX 2000', and without restarting). I have three different
>> sessions
>> below, you can see the different combinations that cause the error to
>> happen..
>>
>> I hope you find this useful.. session #2 is pretty interesting...
>
> An exim -d+lookup -bh SOME.IP.ADDR.ESS session would be more
> useful. But you should check again with a more recent version of exim.
> The caching code was changed in 4.40, some maybe the problem is gone.
And it did go away. I just built 4.42, and the problem is now gone.
Removing lsearch from 4.33 didn't do anything, but it did with 4.42.
Thanks. Oddly enough, I would have upgraded to 4.4x, but I didn't see
anything about the new caching code in the changelogs...
-Eric
