Re: [Exim] how did I screw up?

> > No it's not. $2 = userid $3=pass
> > someone auths to you. $2 is not found in /vrmd/exim/auth thus
> > ${lookup{$2}lsearch{/vrmd/exim/auth}{$value}} = ""
> > they use a blank pass, thus $3 = ""
> > and both match.
> > use this for your lookup:
> > ${lookup{$2}lsearch{/vrmd/exim/auth}{$value}fail}
> >
> > When it sees the "fail", it's forced to fail and the server_condition =
> > fails.
>
> Is this behaviour explained somewhere? Could I write any default-value
> in place of "fail" but only "fail" causes the condition to be skipped?

Yes, I looked it up specifically. Read section 33 (I think that's it).
It's the one for the plaintext authenticator.

a fail does not cause the condition to be skipped, it causes it to fail.
IIRC, a forced failure does the same thing as the string expanding to
false/no/0 (atleast to the client). When debugging, you'll see it was
forced to fail.

try exim -bh 1.2.3.4
then type:
EHLO somehost
AUTH LOGIN
<blank line 2 times>

If you're open, it'll work, if you're not, you can see what happened.

This is assuming you're not doing HELO checking or AUTH checking in ACLs
that would prevent the above from the supposed IP 1.2.3.4

--
Lab tests show that use of micro$oft causes cancer in lab animals