Jason Pruim
pru...@gmail.com
352.234.3175
> On Apr 2, 2016, at 8:01 PM, Alexander Dalloz <ad+li...@uni-x.org> wrote:
>
> Am 03.04.2016 um 01:04 schrieb Jason Pruim:
>>
>> Jason Pruim
>> pru...@gmail.com
>> 352.234.3175
>>
>>
>>> On Apr 2, 2016, at 6:42 PM, Alexander Dalloz <ad+li...@uni-x.org> wrote:
>>>
>>> Am 03.04.2016 um 00:26 schrieb Jason Pruim:
>>>> Hey Edgar,
>>>>
>>>> Thanks for catching that! Missed it earlier! Got it changed but I’m still
>>>> having the same error updated postconf -n:
>>>
>>> Why do you provide the Postfix configuration? Absolutely unrelated to the
>>> shown dovecot error.
>>
>> I provide what I know how to provide :)
>>>
>>>> [ec2-user@ip-172-31-24-2 conf.d]$ postconf -n
>>>> alias_database = hash:/etc/aliases
>>>> alias_maps = hash:/etc/aliases
>>>> command_directory = /usr/sbin
>>>> config_directory = /etc/postfix
>>>> daemon_directory = /usr/libexec/postfix
>>>> data_directory = /var/lib/postfix
>>>> debug_peer_level = 2
>>>> html_directory = no
>>>> inet_interfaces = localhost
>>>> inet_protocols = all
>>>> mail_owner = postfix
>>>> mailq_path = /usr/bin/mailq.postfix
>>>> manpage_directory = /usr/share/man
>>>> mydestination = $myhostname, localhost.$mydomain, localhost
>>>> newaliases_path = /usr/bin/newaliases.postfix
>>>> queue_directory = /var/spool/postfix
>>>> readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES
>>>> sample_directory = /usr/share/doc/postfix-2.6.6/samples
>>>> sendmail_path = /usr/sbin/sendmail.postfix
>>>> setgid_group = postdrop
>>>> unknown_local_recipient_reject_code = 550
>>>> virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
>>>> virtual_mailbox_domains =
>>>> mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
>>>> virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
>>>> virtual_transport = dovecot
>>>> [ec2-user@ip-172-31-24-2 conf.d]$
>>>
>>> While being at Postfix: You have zero SASL configuration, unless it is
>>> defined in master.cf for the submission transport.
>>
>> Lets do 1 problem at a time… Unless SASL is needed for sending email?
>
> Right, 1 problem at a time.
>
> Yes, SASL is needed for your MTA to permit relaying based on authentication.
Okay, I’ll look at that as soon as I get my server allowing me to login! :)
>
>>>> Here is the same error:
>>>>
>>>> Apr 2 22:25:50 ip-172-31-24-2 dovecot: auth: Fatal: Unknown database
>>>> driver 'sql'
>>>> Apr 2 22:25:50 ip-172-31-24-2 dovecot: master: Error: service(auth):
>>>> command startup failed, throttling for 60 secs
>>>> Apr 2 22:25:50 ip-172-31-24-2 dovecot: imap-login: Disconnected: Auth
>>>> process broken (disconnected before auth was ready, waited 9 secs):
>>>> user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<leZR+ocvhwB/AAAB>
>>>
>>> Please provide the output of "doveconf -n". You have a severe configuration
>>> error so that the auth process fails.
>>
>> Here is the output:
>>
>> [ec2-user@ip-172-31-24-2 conf.d]$ dovecot -n
>> # 2.2.10: /etc/dovecot/dovecot.conf
>
> Where did you get that dovecot version from? The Postfix version seems to
> indicate a RHEL/CentOS base of major release 6. That one does not ship a
> dovecot 2.2.x version.
postfix and dovecot were both downloaded from a simple: yum install postfix
dovecot command on my amazon linux server
>
>> # OS: Linux 4.1.17-22.30.amzn1.x86_64 x86_64 ext4
>> auth_mechanisms = plain login
>> mail_location = maildir:/var/vmail/%d/%n/Maildir
>> mbox_write_locks = fcntl
>> namespace inbox {
>> inbox = yes
>> location =
>> prefix =
>> separator = .
>> }
>> passdb {
>> args = /etc/dovecot/dovecot-sql.conf.ext
>
> What specified in the dovecot-sql.conf.ext file? Make sure the driver in
> there is set as "mysql" and not "sql". Not sure whether your dovecot is
> packaged in a way that you need a another package to provide the SQL driver
> functionality.
driver = mysql
connect = host=127.0.0.1 dbname=mailserver user=validsqluser
password=validsqlpassword
default_pass_scheme = PLAIN-MD5
password_query = SELECT email as user, password FROM virtual_users WHERE
email='%u’;
>
> Btw. there is no need to run any SQL based backend, neither for dovecot nor
> Postfix, while I see a lot of beginners to think it would be. Keep it simple,
> even most simple while your are doing your first steps.
The tutorial I found on workaround.org had it hooking up to sql so with me
trying to learn more about all of linux, I thought why the heck not? :) For
hosting multiple domains would it make a difference? I’m planning on hosting 2
from here for starters.
>
>> driver = sql
>> }
>> protocols = imap lmtp
>> service auth {
>> unix_listener /var/spool/postfix/private/auth {
>> group = postfix
>> mode = 0660
>> user = postfix
>> }
>> unix_listener auth-userdb {
>> group = postfix
>> mode = 0600
>> user = postfix
>> }
>> user = dovecot
>> }
>> service imap-login {
>> inet_listener imap {
>> port = 143
>> }
>> inet_listener imaps {
>> port = 993
>> }
>> }
>> service lmtp {
>> unix_listener /var/spool/postfix/private/dovecot-lmtp {
>> group = postfix
>> mode = 0600
>> user = postfix
>> }
>> }
>> ssl = no
>> ssl_cert = </etc/pki/dovecot/certs/dovecot.pem
>> ssl_key = </etc/pki/dovecot/private/dovecot.pem
>> ssl_protocols = !SSLv2 !SSLv3
>> userdb {
>> args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n
>> driver = static
>> }
>> protocol lmtp {
>> mail_plugins = " sieve"
>> }
>> protocol lda {
>> mail_plugins = " sieve"
>> }
>> [ec2-user@ip-172-31-24-2 conf.d]$
>>
>>
>> It’s been awhile since I’ve run a mail server, and never to this extent…
>> Always through hosting companies except for about 15 years ago when I did it
>> for fun! :)
>>
>> Thanks for all your help!
>
> Regards
>
> Alexander
Thanks Alexander!
