[Exim] Exim 4.23 and IMAP/POP on Suse 8.2 Question

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Tom Ray [Lists]
Date:  
À: exim-users
Sujet: [Exim] Exim 4.23 and IMAP/POP on Suse 8.2 Question
Hey all, I'm having a small problem with Exim 4.23 and IMAP/POP with
virtual domains on a Suse 8.2 box. I've installed Exim before and have
gotten IMAP/Pop with virtual domains to work before, but this is my
first Suse setup...normally it was RedHat. Basically, I've gotten
everything working properly. Mail is delivered without error, forwarding
is working great, however, it's logging in to the box and getting the
mail is where I'm running into my snag.

I'm using plaintext (yeah I know) and I saw that Suse 8.2 has plaintext
disabled but you can overwrite it which I did. But even with that it
still fails on login it. What it looks like in the log file is that it's
not parsing the email out when I pass the username as tom@???.
Which leads to me to believe since the login routers don't know which
domain to check they can't open the proper password file to figure
things out.

This is what I have in my configure file for Exim under Authenticators:

begin authenticators

plain:
driver = plaintext
public_name = PLAIN
server_condition="${if and
{{eq{${lookup{${domain:$1}}lsearch{/etc/exim/smtp_auth_domains}}}{yes}}{crypteq{$2}{${extract{1}{:}{\

${lookup{${local_part:$1}}lsearch{/webs/${domain:$1}/etc/passwd}{$value}}}}}}}
\
                {yes}{no}}"


server_set_id = $1

login:
driver = plaintext
public_name = LOGIN
server_prompts = "Username:: : Password::"

server_condition="${if and
{{eq{${lookup{${domain:$1}}lsearch{/etc/exim/smtp_auth_domains}}}{yes}}{crypteq{$2}{${extract{1}{:}{\

${lookup{${local_part:$1}}lsearch{/webs/${domain:$1}/etc/passwd}{$value}}}}}}}
\
                {yes}{no}}"


server_set_id = $1


And I'm getting this wonderful error in my log file...

Jan 10 18:15:42 mx01-new ipop3d[6080]: Command stream end of file while
reading line user=tom@??? host=hidden(by me) :)

I've been scratching my head over this for the last two days...anyone
ever had to deal with this, or might be able to offer suggestion in a
work around. Please let me know if you ever dealt with something like
this, any suggestions would be great. Or if you might know a work around
for this.

TIA