On Saturday, March 26, 2016 1:04 PM, MARIA jamieson <jamieson.maria@yahoo.com> wrote:
Yes, I am trying it over ssl. Everything works as in I can connect to my mail server and establish an ssl connection. There's no error with SSL. It's just auth mechanism having a environment corruption error. I am not the only one. You can google around and find many run into this situation and no one could help. Most just delete the dovecot and postfix and start over again. However, I cannot afford that because it took me at least 3 months to setup dovecot correctly with postfix to use virtual users. I don't have the time to spend another 3 months to set it up. The problem lies with auth and I think this is the only issue and it has to be that something is missing either in the configs or a file was deleted or link to it was broken. I am sure after fixing this issue. I will have a working mail system again.
On Saturday, March 26, 2016 2:40 AM, Aki Tuomi <aki.tuomi@dovecot.fi> wrote:
You should reply to list and not just me. Did you try over SSL? ---Aki TuomiDovecot oy-------- Alkuperäinen viesti --------Lähettäjä: MARIA jamieson jamieson.maria@yahoo.com Päivämäärä: 26.3.2016 6.28 (GMT+02:00) Saaja: aki.tuomi@dovecot.fi Aihe: Re: Need help solving issue doveconf -n output: doveconf -n # 2.2.18: /local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: FreeBSD 10.2-RELEASE amd64 ufs auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes default_login_user = dovecot dict { quota = mysql:/local/etc/dovecot-dict-quota.conf } disable_plaintext_auth = no first_valid_gid = 125 first_valid_uid = 125 info_log_path = /var/log/dovecot.log log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:/local/virt/%d/%n/ mail_privileged_group = mail 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 index ihave duplicate passdb { args = /local/etc/dovecot/dovecot-sql.conf driver = sql name = sql } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = mode = 0600 user = } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } ssl = required ssl_cert =
On Friday, March 25, 2016 2:41 PM, "aki.tuomi@dovecot.fi" <aki.tuomi@dovecot.fi> wrote:
On March 25, 2016 at 6:48 PM MARIA jamieson jamieson.maria@yahoo.com wrote:
Hi, I am using Dovecot 2.2.18 and have migrated from a 1.x versions. After this migration I had several errors and obsolete errors in logs. I fixed them and after all that I finally was able to run postfix and dovecot again. The problem I have facing right now is that in the mail logs and in the dovecot logs. I am getting auth errors. In mail log the postfix is spitting out: " fatal: no SASL authentication mechanisms" Dovecot is spitting this out "imap-login : Auth process broken (disconnected before auth was ready, waited 0 secs): ,user<>, the shows client ip, my server ip and then the 0 seconds connection etc. Error: auth: environment corrupt; missing value for DOVECOT_"
That is what it spits out. I asked for help and many threads.I am using freebsd 10.2. I do use mysql for database. I need someone to explain what the error means and how I can fix it? Thank you for your time!
Hi!
Can you provide your postconf -n and doveconf -n output? This sounds like configuration error.
Aki Tuomi Dovecot Oy
On Sat, 26 Mar 2016 17:28:29 +0000 (UTC), MARIA jamieson stated:
Yes, I am trying it over ssl. Everything works as in I can connect to my mail server and establish an ssl connection. There's no error with SSL. It's just auth mechanism having a environment corruption error. I am not the only one. You can google around and find many run into this situation and no one could help. Most just delete the dovecot and postfix and start over again. However, I cannot afford that because it took me at least 3 months to setup dovecot correctly with postfix to use virtual users. I don't have the time to spend another 3 months to set it up. The problem lies with auth and I think this is the only issue and it has to be that something is missing either in the configs or a file was deleted or link to it was broken. I am sure after fixing this issue. I will have a working mail system again.
Postfix offers excellent debugging strategies. http://www.postfix.org/DEBUG_README.html. Have you read it? Pay particular attention to: http://www.postfix.org/DEBUG_README.html#mail.
Note item #8, "If the problem is SASL related, consider including the output from the saslfinger tool. This can be found at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/." Give that a shot then report back the results.
-- Jerry
what's the difference between sasl and auth mech in dovecot? Postfix points to a sasl problem and dovecot points to a auth mechanism saying it's corrupted. I did looked at the links you provided. I don't have the tools and don't have time right now to fiddle with them and run them to get a result at this time.
On Saturday, March 26, 2016 4:32 PM, Jerry <jerry@seibercom.net> wrote:
On Sat, 26 Mar 2016 17:28:29 +0000 (UTC), MARIA jamieson stated:
Yes, I am trying it over ssl. Everything works as in I can connect to my mail server and establish an ssl connection. There's no error with SSL. It's just auth mechanism having a environment corruption error. I am not the only one. You can google around and find many run into this situation and no one could help. Most just delete the dovecot and postfix and start over again. However, I cannot afford that because it took me at least 3 months to setup dovecot correctly with postfix to use virtual users. I don't have the time to spend another 3 months to set it up. The problem lies with auth and I think this is the only issue and it has to be that something is missing either in the configs or a file was deleted or link to it was broken. I am sure after fixing this issue. I will have a working mail system again.
Postfix offers excellent debugging strategies. http://www.postfix.org/DEBUG_README.html. Have you read it? Pay particular attention to: http://www.postfix.org/DEBUG_README.html#mail.
Note item #8, "If the problem is SASL related, consider including the output from the saslfinger tool. This can be found at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/." Give that a shot then report back the results.
-- Jerry
participants (2)
-
Jerry
-
MARIA jamieson