Hi Jeremy,First off, I really appreciate the quick response and thank you for all your help.
I tried changing the $1 and $2 to $auth1 and 2 respectfully. I still get the same outcome (the virtual user cannot send email but the general user can).
I may be missing the boat entirely here but it seems to me that this machine isn't reading the password file correctly. The configuration that I used on the previous machine used the same password file for both dovecot and exim. For some reason,on the new machine, dovecot didn't like the default (MD5 password hash) that was used so I had to change it to SHA. So, I separated the files into 2. The dovecot one is in SHA and the Exim one is the MD5 hash that I created but it still doesn't like reading it (I tried a SHA file for Exim and got the same results). I have the permissions for that file set the same as they were on the old machine. I don't think (although again, I may be missing the boat entirely) that the logic is at fault, I am really leaning towards the password file.
Please tell me if I'm off base or not. Thanks, Brian On 2/10/2015 7:20 AM, Jeremy Harris wrote:
On 09/02/15 21:21, Brian Rudy wrote:server_condition = "\ ${if exists{/etc/exim/vuserspwd}\ {${lookup{$1}lsearch{/etc/exim/vuserspwd}\ {${if crypteq{$auth2}{\\\{crypt\\\}${extract{1}{:}{$value}{$value}fail}}\ {true}{false} }}\ {${if saslauthd{{$1}{$2}{smtp}} {1}}}}}}"Should those $1 & $2 actually be $auth1 & $auth2 ? Can you test that expansion, using "exim -be" and some appropriate values for $1 and $2? If that bit works then dig a bit deeper with section 4 of http://exim.org/exim-html-current/doc/html/spec_html/ch-smtp_authentication.html
smime.p7s
Description: S/MIME Cryptographic Signature
-- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
