Authenticated SMTP with Exim and Dovecot

[dha...@gmail.com]

Hello everyone

I'm setting up a new mail server with the goal of using Exim's dovecot driver to centralize authentication. TLS is setup and enabled on both sides.

It seems straight forward from this link:
http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL



However, after I follow those steps I'm getting the following error in the log

dovecot_login authenticator failed for ("host") ["ip"]: 435 Unable to authenticate at present: authentication socket connection error



I am able to receive mail, and use dovecot+mysql for authentication on any mail client. I'm just stuck at what I'm missing to allow authenticated users to send mail through this server.


-- my system stats ---
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-358.14.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) ext4


Exim version 4.72 #1 built 28-Oct-2012 18:32:26
Copyright (c) University of Cambridge, 1995 - 2007
Berkeley DB: Berkeley DB 4.7.25: (March 5, 2012)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc TCPwrappers OpenSSL Content_Scanning DKIM Old_Demime
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch ldap ldapdn ldapm nis nis0 nisplus passwd sqlite
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
OpenSSL compile-time version: OpenSSL 1.0.0-fips 29 Mar 2010
OpenSSL runtime version: OpenSSL 1.0.0-fips 29 Mar 2010
Configuration file is /etc/exim/exim.conf





thanks

[Lemat]

dha...@gmail.com wrote:

> Hello everyone
>
> I'm setting up a new mail server with the goal of using Exim's dovecot
> driver to centralize authentication. TLS is setup and enabled on both
> sides.
>
> It seems straight forward from this link:
> http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL
>
>
>
> However, after I follow those steps I'm getting the following error in the
> log
>
> dovecot_login authenticator failed for ("host") ["ip"]: 435 Unable to
> authenticate at present: authentication socket connection error
>

check if file exists & adjust file permissions to
/var/run/dovecot/auth-client
in dovecot config (mode,user,group)

--
Pozdrawiam
Lemat
Zanim zadasz pytanie: proszę o informację, jaka była przyczyna śmierci
Twojego ostatniego niewolnika.

[dha...@gmail.com]

Thank you Lemat. The file did exist, and I relaxed permission on it a bit and just sent a test message from my webmail client.

Now I'm running into a relay issue when I attempt to use my phone and send a test email

"rejected RCPT <(Email address)>: relay not permitted"

What am I missing to allow an authenticated user to send email from this server?

I understand why the webmail client sent mail because of this exim setting
hostlist relay_from_hosts = 127.0.0.1


How do I relay once a user is authenticated since I won't know the host ahead of time?





On Wednesday, August 21, 2013 6:32:20 PM UTC-4, Lemat wrote:

[horhe]

W dniu 22.08.2013 01:14, dha...@gmail.com pisze:

> Thank you Lemat. The file did exist, and I relaxed permission on it a bit and just sent a test message from my webmail client.
>
> Now I'm running into a relay issue when I attempt to use my phone and send a test email
>
> "rejected RCPT <(Email address)>: relay not permitted"
>
> What am I missing to allow an authenticated user to send email from this server?
>
> I understand why the webmail client sent mail because of this exim setting
> hostlist relay_from_hosts = 127.0.0.1
>
>
> How do I relay once a user is authenticated since I won't know the host ahead of time?

You didn't show us exim.conf so I'm guessing you need in
"acl_check_rcpt" section something like this:
accept
authenticated = *
control = submission/sender_retain

[dha...@gmail.com]

It looks like the combo of sender_retain and commenting out the default dkim_disable_verify did the trick

Thanks all




On Thursday, August 22, 2013 3:59:50 AM UTC-4, horhe wrote:
> W dniu 22.08.2013 01:14, dhcom pisze: