great tip, thank you.
My session looks like this(names changed):
.
.
.
AUTH LOGIN
334 VXNlcm5hbWU6IDsgUGFasdfasdf6
cmFuZGFs
login authenticator:
$1 = randal
expanded string: myPassword
435 Unable to authenticate at present: myPassword
LOG: MAIN REJECT
login authenticator failed for (localhost) [127.0.0.1]: 435 Unable to
authenticate at present (set_id=randal): myPassword
So it does some back with the correct password, but still fails somehow...?
Any further ideas?
Peter Savitch wrote:
> Hello,
>
> The conf fragment provided by Tony is correct.
> You can use whatever delimiter you like, but these *really* known to
> work:
>
> server_prompts = <; Username: ; Password:
> server_prompts = <| Username: ; Password:
> server_prompts = <, Username: , Password:
>
> You have to trace the things up, using tcpdump, Exim native debugging,
> and so on.
>
> That's for Exim:
>
> exim -bh 127.0.0.1 -d-all+auth
>
> Say "EHLO localhost" and proceed with "AUTH LOGIN", followed by
> base64-encoded username and password, each on a separate line. If you
> see something like "AUTH command used when not advertised", refer to TFM
> ;-)
>
> And that's for raw tcpdump session hijacking:
> tcpdump -i eth0 -s 1500 -l -w - port 25 | strings
>
> You need a package (like metamail) that allows you to encode/decode
> base64 strings for the LOGIN authenticator. See mimencode(1).
>
> The exact reason could lie under your Perl stuff.
>
>
>>Thanks for this, but it is still giving the same error and not
>
> allowing
>
>>authentication.
>>
>>Tony Finch wrote:
>>
>
> [snip]
>
>>> server_prompts = <| Username: | Password:
>
>
