Milter-greylist

manu@... a \ufffdcrit :
> Benoit Branciard <benoit.branciard@...> wrote:
> 
>> My scripts output only \n's, and I just verified Apache didn't mangle
>> them to something else.
>>
>> Should they send \r\n's ?
> 
> No, it was just an idea. 
> Could it be that it's just the last char that get mangled? What happens
> if you stick a single space at the end of the line, instead of adding a
> blank line?
> 


1)

-- urlcheck script:
echo "milterGreylistStatus: Ok "
echo "milterGreylistMsg: You are not allowed to connect "

-- log:
milter-greylist: ignoring unepxected "milterGreylistStatus" => "Ok "
milter-greylist: ignoring unepxected "" => "You are not allowed to connect"

-- action:
both statements are ignord, message passes.


2)

-- urlcheck script:
echo " milterGreylistStatus: Ok"
echo " milterGreylistMsg: You are not allowed to connect"


-- log:
milter-greylist: ignoring unepxected "" => "You are not allowed to connec"

-- action:
milterGreylistStatus is honoured, milterGreylistMsg is not


more leading spaces (I tested 2 and 10) give similar result, but error 
message in log vary slightly (first "" argument seems to contain random 
1- or 2-char stings)


Conclusions (if any):

- milter-greylist does not cope with trailing spaces, it causes 
milterGreylistStatus statement value to be ignored. Actually the code in 
  urlcheck.c seems to skip leadins spaces (at beginning of line and 
after ":"), but not at end of line.

- leading spaces do not solve problem

- I can't see a logic in the bug for the moment

-- 
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.