New dovecot user needs installation help
Hey Everyone, So I just setup my first dovecot install with postfix running for the mail server… I can telnet into my dovecot install and login just fine with my user locally… But when I try to add the account from my phone, computer, or telnetting from my local computer, it just hangs and eventually kicks back a generic error saying it can’t be added… Where can I start looking? I’m hosted with amazon web services and I’m waiting on them to approve my request to white list my IP on my instance, but that should only restrict my ability to send email out on port 25… I should still be able to operate locally… According to the firewall on amazon port 143 and 993 are both allowed from any IP address into the server (All outbound traffic is currently open until I get it working) I’m thinking it’s something easy, and I can handle pointers! I don’t necessarily need my hand held the entire way… At least not yet… Here is the output of my dovecot -n: [ec2-user@ip-172-31-22-222 log]$ dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 3.14.48-33.39.amzn1.x86_64 x86_64 mail_location = mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { driver = pam } ssl_cert =
Re: New dovecot user needs installation help
Sent from my iPhone > On Mar 15, 2016, at 3:22 AM, Steffen Kaiser > wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > >> On Mon, 14 Mar 2016, Jason Pruim wrote: >> >> So I just setup my first dovecot install with postfix running for the mail >> server… I can telnet into my dovecot install and login just fine > > what does "telnet into my dovecot install" mean exacly? I used telnet to connect to port 143 and issued some smtp commands including logging into an account. > > Did you've read: > http://wiki2.dovecot.org/TestInstallation I did yes... But I will go back over it tonight when I get back home. > >> with my user locally… But when I try to add the account from my phone, >> computer, or telnetting from my local computer, it just hangs and eventually >> kicks back a generic error saying it can’t be added… Where can I start >> looking? I’m hosted with amazon web services and I’m waiting on them to >> approve my request to white list my IP on my instance, but that should only >> restrict my ability to send email out on port 25… I should still be able to >> operate locally… >> >> >> According to the firewall on amazon port 143 and 993 are both allowed from >> any IP address into the server (All outbound traffic is currently open until >> I get it working) >> >> I’m thinking it’s something easy, and I can handle pointers! I don’t >> necessarily need my hand held the entire way… At least not yet… >> >> Here is the output of my dovecot -n: >> >> [ec2-user@ip-172-31-22-222 log]$ dovecot -n >> # 2.0.9: /etc/dovecot/dovecot.conf >> # OS: Linux 3.14.48-33.39.amzn1.x86_64 x86_64 >> mail_location = mbox:~/mail:INBOX=/var/mail/%u >> mbox_write_locks = fcntl >> passdb { >> driver = pam >> } >> ssl_cert = > ssl_key = > userdb { >> driver = passwd >> } >> [ec2-user@ip-172-31-22-222 log]$ >> >> >> >> >> Let me know if there is anything else you need, or where to go from here! >> >> Thanks in advance! >> >> Jason Pruim >> pru...@gmail.com > > - -- Steffen Kaiser > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQEVAwUBVue4MHz1H7kL/d9rAQJ/8AgAgyDbtTpEbzm7ZFQNQsIhVm2ofEewc9mt > Gplv/Wl46scIfF6tl5NvruoAu3ogQDMoMNnlpZ9cMTWhOrBxXhL3usBRhgB6MnaD > nEuTStYXLCgKS90DLZB0xWvzbhAhqLNu9ohbjW7Al4iWwvl2A4tSrgJAWwNLJsAi > VpDQ9ha41zzu2ZqjH9J8PepVoQS47ZDauiGtPinTVQ8aMI40uLB1L5gFLfuVm0rM > l/f0JsK/SYKPkE1j+yow61zpqOFnCbYOMlck526RGP7nJZIo0MLfCwt68j8C0TPh > HxnRsL9jkvuufgB3zTvcdCYgHgODB0oP/AGtQPnXXo10HvsqdoBapA== > =N+EP > -END PGP SIGNATURE- Thanks for taking the time to look!
Re: New dovecot user needs installation help
This is all it’s showing me in the log: [ec2-user@ip-172-31-22-222 ~]$ sudo tail -f /var/log/maillog Mar 15 20:39:41 ip-172-31-22-222 dovecot: doveadm: Debug: This is Dovecot's debug log (1458074381) Mar 15 20:39:41 ip-172-31-22-222 dovecot: doveadm: This is Dovecot's info log (1458074381) Mar 15 20:39:41 ip-172-31-22-222 dovecot: doveadm: Warning: This is Dovecot's warning log (1458074381) Mar 15 20:39:41 ip-172-31-22-222 dovecot: doveadm: Error: This is Dovecot's error log (1458074381) Mar 15 20:39:41 ip-172-31-22-222 dovecot: doveadm: Fatal: This is Dovecot's fatal log (1458074381) Mar 15 20:39:50 ip-172-31-22-222 dovecot: doveadm: Debug: This is Dovecot's debug log (1458074390) Mar 15 20:39:50 ip-172-31-22-222 dovecot: doveadm: This is Dovecot's info log (1458074390) Mar 15 20:39:50 ip-172-31-22-222 dovecot: doveadm: Warning: This is Dovecot's warning log (1458074390) Mar 15 20:39:50 ip-172-31-22-222 dovecot: doveadm: Error: This is Dovecot's error log (1458074390) Mar 15 20:39:50 ip-172-31-22-222 dovecot: doveadm: Fatal: This is Dovecot's fatal log (1458074390) Mar 15 20:41:53 ip-172-31-22-222 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=1561, secured I just logged in and ran the commands. you can see my login, but it’s not logging any errors… Although it won’t let me select my inbox on that user… Jason Pruim pru...@gmail.com 352.234.3175 > On Mar 15, 2016, at 1:06 AM, Aki Tuomi wrote: > > Can yoi run doveadm log errors too? > > > > --- > Aki Tuomi > Dovecot oy > > Alkuperäinen viesti > Lähettäjä: Jason Pruim > Päivämäärä: 15.3.2016 4.50 (GMT+02:00) > Saaja: dovecot@dovecot.org > Aihe: New dovecot user needs installation help > > Hey Everyone, > > So I just setup my first dovecot install with postfix running for the mail > server… I can telnet into my dovecot install and login just fine with my user > locally… But when I try to add the account from my phone, computer, or > telnetting from my local computer, it just hangs and eventually kicks back a > generic error saying it can’t be added… Where can I start looking? I’m hosted > with amazon web services and I’m waiting on them to approve my request to > white list my IP on my instance, but that should only restrict my ability to > send email out on port 25… I should still be able to operate locally… > > > According to the firewall on amazon port 143 and 993 are both allowed from > any IP address into the server (All outbound traffic is currently open until > I get it working) > > I’m thinking it’s something easy, and I can handle pointers! I don’t > necessarily need my hand held the entire way… At least not yet… > > Here is the output of my dovecot -n: > > [ec2-user@ip-172-31-22-222 log]$ dovecot -n > # 2.0.9: /etc/dovecot/dovecot.conf > # OS: Linux 3.14.48-33.39.amzn1.x86_64 x86_64 > mail_location = mbox:~/mail:INBOX=/var/mail/%u > mbox_write_locks = fcntl > passdb { > driver = pam > } > ssl_cert = ssl_key = userdb { > driver = passwd > } > [ec2-user@ip-172-31-22-222 log]$ > > > > > Let me know if there is anything else you need, or where to go from here! > > Thanks in advance! > > Jason Pruim > pru...@gmail.com
Re: New dovecot user needs installation help
Jason Pruim pru...@gmail.com 352.234.3175 > On Mar 15, 2016, at 8:21 AM, Steffen Kaiser > wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, 15 Mar 2016, Jason Pruim wrote: >>> On Mar 15, 2016, at 3:22 AM, Steffen Kaiser >>> wrote: >>> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>>> On Mon, 14 Mar 2016, Jason Pruim wrote: >>>> >>>> So I just setup my first dovecot install with postfix running for the mail >>>> server… I can telnet into my dovecot install and login just fine >>> >>> what does "telnet into my dovecot install" mean exacly? >> >> I used telnet to connect to port 143 and issued some smtp commands including >> logging into an account. > > I issued SMTP commands on port 143 ? telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. a login "beth" "beth4338" a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in select inbox select BAD Error in IMAP command INBOX: Unknown command. > >>> >>> Did you've read: >>> http://wiki2.dovecot.org/TestInstallation >> >> I did yes... But I will go back over it tonight when I get back home. >>> >>>> with my user locally… But when I try to add the account from my phone, >>>> computer, or telnetting from my local computer, it just hangs and >>>> eventually kicks back a generic error saying it can’t be added… Where can >>>> I start looking? I’m hosted with amazon web services and I’m waiting on >>>> them to approve my request to white list my IP on my instance, but that >>>> should only restrict my ability to send email out on port 25… I should >>>> still be able to operate locally… >>>> >>>> >>>> According to the firewall on amazon port 143 and 993 are both allowed from >>>> any IP address into the server (All outbound traffic is currently open >>>> until I get it working) >>>> >>>> I’m thinking it’s something easy, and I can handle pointers! I don’t >>>> necessarily need my hand held the entire way… At least not yet… >>>> >>>> Here is the output of my dovecot -n: >>>> >>>> [ec2-user@ip-172-31-22-222 log]$ dovecot -n >>>> # 2.0.9: /etc/dovecot/dovecot.conf >>>> # OS: Linux 3.14.48-33.39.amzn1.x86_64 x86_64 >>>> mail_location = mbox:~/mail:INBOX=/var/mail/%u >>>> mbox_write_locks = fcntl >>>> passdb { >>>> driver = pam >>>> } >>>> ssl_cert = >>> ssl_key = >>> userdb { >>>> driver = passwd >>>> } >>>> [ec2-user@ip-172-31-22-222 log]$ > > - -- Steffen Kaiser > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQEVAwUBVuf+Ynz1H7kL/d9rAQLCAQgAy/MZhOYJHjtIYK3L7149W7UiXtn50WBR > 4bq9322YfcxtCWeGGsVdz5q/IM7Sz1WnQR5tFGd3LhaMb/g5FjOUzMGZiAaz3Qwu > AcrC+VVYT1cDhXj/7IMRnKvWWH1l0caSU54rGiKrp5lWKOqmGDabxwYEKFnV8aRC > Y3RXu+ZQSVaDjHxnwG8ydFGdRTjkJ5w4GndJG5xPJm6W+56QjEgXgerTeQkCx3vf > mMHqg3BqJ5jWC1cVmnix3kMSpZvlJDRLmc/YIv7Ycvkic+QPisO27b5Wmmgb79GH > OtOTiotR7thlO/ktP16OLuj8oGPVislBcXDfliyDYkLEg6koRbuZWg== > =fu00 > -END PGP SIGNATURE-
First dovecot install
Hey Everyone, I am trying to get postfix and dovecot to talk to each other… postfix is up and running, dovecot allows me to telnet into it both locally and remotely, but when I try to do: “a login “username” “password” I get an authentication failed error… Here is my dovecot -n: [ec2-user@ip-172-31-24-2 dovecot]$ dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 4.1.17-22.30.amzn1.x86_64 x86_64 auth_debug_passwords = yes auth_mechanisms = plain login first_valid_uid = 200 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_gid = 12 mail_home = /mnt/vmail/%d/%n mail_location = maildir:~ mail_uid = 200 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { autocreate = Trash autocreate2 = Sent autocreate3 = Junk autosubscribe = Trash autosubscribe2 = Sent autosubscribe3 = Junk sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/global/ sieve_global_path = /etc/dovecot/sieve/default.sieve sieve_max_script_size = 1M } protocols = imap lmtp sieve pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = ec2-user } unix_listener auth-userdb { group = mail mode = 0600 user = mailreader } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert =
Still muddling through with broken auth...
Hey Everyone, I’m still muddling through my first install… Followed the tutorials on workaround.org <http://workaround.org/> which were very helpful! but don’t include much info if things don’t work 100%… and so far I haven’t been able to pin down where the error is. When I try: telnet localhost 143 this is what shows up in the maillot: Apr 2 21:06:57 ip-172-31-24-2 dovecot: auth: Fatal: Unknown database driver 'sql' Apr 2 21:06:57 ip-172-31-24-2 dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs Apr 2 21:06:57 ip-172-31-24-2 dovecot: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<+lw34IYvVgB/AAAB> With the failed driver for the database, I tried mysql and sql both of which produce the same error… I have a few other issues but I think those are related farther upstream… Not being able to sign into round cube for webmail, because of it being unable to connect to the storage container… But I think that’s a round cube issue… I want to get postfix and dovecot playing nicely before I worry too much about things like webmail access… Here is my postconf -n: [ec2-user@ip-172-31-24-2 dovecot]$ 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_mailbox_domains = hash:/etc/postfix/virtual_mailbox_domains virtual_mailbox_maps = hash:/etc/postfix/virtual_mailbox_users virtual_transport = dovecot [ec2-user@ip-172-31-24-2 dovecot]$ What else can I provide? Thanks! Jason Pruim pru...@gmail.com 352.234.3175
Re: Still muddling through with broken auth...
Hey Edgar, Thanks for catching that! Missed it earlier! Got it changed but I’m still having the same error updated postconf -n: [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]$ 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= I feel like I’m missing something simple but can’t see the forest through the trees… Jason Pruim pru...@gmail.com 352.234.3175 > On Apr 2, 2016, at 5:54 PM, Edgar Pettijohn wrote: > > > > Sent from my iPhone > >> On Apr 2, 2016, at 4:11 PM, Jason Pruim wrote: >> >> Hey Everyone, >> >> I’m still muddling through my first install… Followed the tutorials on >> workaround.org <http://workaround.org/> which were very helpful! but don’t >> include much info if things don’t work 100%… and so far I haven’t been able >> to pin down where the error is. When I try: telnet localhost 143 this is >> what shows up in the maillot: >> >> Apr 2 21:06:57 ip-172-31-24-2 dovecot: auth: Fatal: Unknown database driver >> 'sql' >> Apr 2 21:06:57 ip-172-31-24-2 dovecot: master: Error: service(auth): >> command startup failed, throttling for 2 secs >> Apr 2 21:06:57 ip-172-31-24-2 dovecot: imap-login: Disconnected: Auth >> process broken (disconnected before auth was ready, waited 0 secs): user=<>, >> rip=127.0.0.1, lip=127.0.0.1, secured, session=<+lw34IYvVgB/AAAB> >> >> With the failed driver for the database, I tried mysql and sql both of which >> produce the same error… I have a few other issues but I think those are >> related farther upstream… Not being able to sign into round cube for >> webmail, because of it being unable to connect to the storage container… But >> I think that’s a round cube issue… I want to get postfix and dovecot playing >> nicely before I worry too much about things like webmail access… >> >> Here is my postconf -n: >> >> [ec2-user@ip-172-31-24-2 dovecot]$ 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_mailbox_domains = hash:/etc/postfix/virtual_mailbox_domains >> virtual_mailbox_maps = hash:/etc/postfix/virtual_mailbox_users >> virtual_transport = dovecot >> [ec2-user@ip-172-31-24-2 dovecot]$ > > > I don't use postfix, but I'm guessing the above hash:/etc/ should probably be > some form of mysql:/etc/... > >> >> What else can I provide? >> >> Thanks! >> >> >> >> Jason Pruim >> pru...@gmail.com >> 352.234.3175
Re: Still muddling through with broken auth...
Jason Pruim pru...@gmail.com 352.234.3175 > On Apr 2, 2016, at 6:42 PM, Alexander Dalloz 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? > >> 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= > > 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 # 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 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 =
Re: Still muddling through with broken auth...
Jason Pruim pru...@gmail.com 352.234.3175 > On Apr 2, 2016, at 8:01 PM, Alexander Dalloz 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 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= >>> >>> 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 b
Re: Still muddling through with broken auth...
>> >>> 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 = >>> ssl_key = >>> 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! > > Make sure MySQL is running and configured correctly as well. Logged in as the same user and was able to run the 3 sql commands that are in the config files…. Best as I can tell it’s up and running properly.
Re: Still muddling through with broken auth...
Jason Pruim pru...@gmail.com 352.234.3175 > On Apr 2, 2016, at 9:06 PM, Alexander Dalloz wrote: > > Am 03.04.2016 um 02:07 schrieb Jason Pruim: >> >> Jason Pruim >> pru...@gmail.com >> 352.234.3175 > > Please answer just to the mailing list and omit to copy your replies to my > personal address too. Thanks. My apologies, I had been hitting reply all. > >>>>>> 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= > > rpm -qlv dovecot | grep libdovecot-sql > > That should print out something like > > lrwxrwxrwx1 rootroot 23 Apr 1 03:29 > /usr/lib64/dovecot/libdovecot-sql.so.0 -> libdovecot-sql.so.0.0.0 > -rwxr-xr-x1 rootroot95058 Apr 1 03:29 > /usr/lib64/dovecot/libdovecot-sql.so.0.0.0 > > If no libdovecot-sql.so is included, then SQL support is missing in that > dovecot package. > > Alexander I started going back over the same tutorial and reran the commands including this one: postconf -e virtual_alias_maps=mysql:/etc/postfix/mysql-virtual-alias-maps.cf,mysql:/etc/postfix/mysql-email2email.cf and as soon as that one hit I was able to login! Now I just need to get it accepting email and sending email! Thank you for your help and for putting up with my lack of knowledge!
1 last error
Hey Everyone, I’m down to 1 last error that I know I created on my own but I can’t figure out how to fix it… Here is the error that I’m getting: Apr 3 04:29:37 ip-172-31-24-2 postfix/qmgr[20458]: EFE01423E2: from=, size=359, nrcpt=1 (queue active) Apr 3 04:29:37 ip-172-31-24-2 dovecot: lda(b...@primelashdiva.info): Fatal: setresgid(89(postfix),89(postfix),97(dovecot)) failed with euid=97(dovecot): Operation not permitted Apr 3 04:29:37 ip-172-31-24-2 postfix/pipe[20745]: EFE01423E2: to=, relay=dovecot, delay=22, delays=22/0.01/0/0.01, dsn=4.3.0, status=deferred (temporary failure) So I figure that I messed up the permissions on /etc/dovecot/conf.d I tried to fix it even by setting it way open: drwxrwxrwx 2 dovecot dovecot 4096 Mar 30 00:56 conf.d And it still doesn’t work! doveconf -n: $ doveconf -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 4.1.17-22.30.amzn1.x86_64 x86_64 ext4 auth_mechanisms = plain login first_valid_uid = 89 hostname = mail.primelashdiva.info mail_location = maildir:/var/vmail/%d/%n/Maildir mail_privileged_group = dovecot mbox_write_locks = fcntl namespace inbox { inbox = yes location = prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } postmaster_address = postmas...@primelashdiva.info protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = dovecot mode = 0666 user = dovecot } 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 =
Re: 1 last error
Jason Pruim pru...@gmail.com 352.234.3175 > On Apr 3, 2016, at 6:49 AM, aki.tu...@dovecot.fi wrote: > > >> On April 3, 2016 at 7:38 AM Jason Pruim wrote: >> >> >> Hey Everyone, >> >> I’m down to 1 last error that I know I created on my own but I can’t figure >> out how to fix it… Here is the error that I’m getting: >> >> Apr 3 04:29:37 ip-172-31-24-2 postfix/qmgr[20458]: EFE01423E2: >> from=, size=359, nrcpt=1 (queue active) >> Apr 3 04:29:37 ip-172-31-24-2 dovecot: lda(b...@primelashdiva.info): Fatal: >> setresgid(89(postfix),89(postfix),97(dovecot)) failed with euid=97(dovecot): >> Operation not permitted > > This means that dovecot is not permitted to use group 89. Is dovecot user > member > of this group? Yes it is. still getting the same error… > >> Jason Pruim >> pru...@gmail.com >> 352.234.3175 > > Aki Tuomi > Dovecot Oy
Unable to login with iPhone?
Hey Everyone, So I have my dovecot install up and running! I can receive mail from the outside, still dealing with a small issue with sending email, but I think that's an issue off needing to setup a relay... Right now though... My biggest issue is it won't connect to my iPhone... I can login with mail on my computer, and through round cube for webmail... But it gets stuck on "verifying"... I tried addingcram-md5 and digest-md5 to the auth_mechanisms but that didn't work... Any idea what I'm missing? Here is my doveconf -n: [ec2-user@ip-172-31-28-46 postfix]$ doveconf -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 4.4.5-15.26.amzn1.x86_64 x86_64 ext4 auth_mechanisms = plain login cram-md5 digest-md5 mail_location = maildir:/var/vmail/%d/%n/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl namespace inbox { inbox = yes location = prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl = required ssl_cert =
Unable to get mail?
Hey everyone, I'm not sure I'm on the right list for this one... I have a postfix/dovecot install that was running fine on amazon web services that all of a sudden stopped receiving mail... In my mail log all I get is this: Apr 30 03:16:26 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Connection closed in=595 out=1459 Apr 30 03:16:31 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=31865, TLS, session= Apr 30 03:16:33 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=31867, TLS, session= Apr 30 03:16:34 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=97 out=440 Apr 30 03:16:38 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=31869, TLS, session= Apr 30 03:19:14 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=408 out=1385 Apr 30 03:19:14 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=847 out=3067 Apr 30 03:20:25 ip-172-31-28-46 postfix/postfix-script[3891]: stopping the Postfix mail system Apr 30 03:20:25 ip-172-31-28-46 postfix/master[31225]: terminating on signal 15 Apr 30 03:20:25 ip-172-31-28-46 postfix/postfix-script[3963]: starting the Postfix mail system Apr 30 03:20:25 ip-172-31-28-46 postfix/master[3964]: daemon started -- version 2.6.6, configuration /etc/postfix Apr 30 03:20:44 ip-172-31-28-46 dovecot: master: Warning: Killed with signal 15 (by pid=3977 uid=0 code=kill) Apr 30 03:20:44 ip-172-31-28-46 dovecot: imap: Server shutting down. in=472 out=1366 Apr 30 03:20:45 ip-172-31-28-46 dovecot: master: Dovecot v2.2.10 starting up for imap, pop3, lmtp (core dumps disabled) Apr 30 03:21:17 ip-172-31-28-46 dovecot: imap-login: Aborted login (no auth attempts in 9 secs): user=<>, rip=68.105.170.121, lip=172.31.28.46, session= Apr 30 03:24:30 ip-172-31-28-46 postfix/postfix-script[4141]: stopping the Postfix mail system Apr 30 03:24:30 ip-172-31-28-46 postfix/master[3964]: terminating on signal 15 Apr 30 03:24:30 ip-172-31-28-46 dovecot: master: Warning: Killed with signal 15 (by pid=4147 uid=0 code=kill) Apr 30 03:25:28 ip-172-31-28-46 postfix/postfix-script[2761]: starting the Postfix mail system Apr 30 03:25:28 ip-172-31-28-46 postfix/master[2762]: daemon started -- version 2.6.6, configuration /etc/postfix Apr 30 03:26:22 ip-172-31-28-46 dovecot: master: Dovecot v2.2.10 starting up for imap, pop3, lmtp (core dumps disabled) Apr 30 03:27:03 ip-172-31-28-46 dovecot: imap-login: Aborted login (no auth attempts in 6 secs): user=<>, rip=68.105.170.121, lip=172.31.28.46, session= Apr 30 03:27:36 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=3001, TLS, session= Apr 30 03:27:54 ip-172-31-28-46 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session= Apr 30 03:28:06 ip-172-31-28-46 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session= Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3008, secured, session= Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=29 out=466 Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3011, secured, session= Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=44 out=538 Apr 30 03:28:11 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3014, secured, session= Apr 30 03:28:11 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=314 out=6899 Apr 30 03:28:12 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3017, secured, session= Apr 30 03:28:12 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=209 out=816 Apr 30 03:29:12 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3024, secured, session= Apr 30 03:29:12 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:30:12 ip-172-31-28-46 dovecot: imap-login: Login: user=< b...@primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3027, secured, session=<9r6GYKsxsAB/AAAB> Apr 30 03:30:12 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info): Dis