- dovecot - dovecot.org

Dovecot on FreeBSD 10.1
by Larry Rosenman 27 Mar '16

27 Mar '16

I'll take a look when I get home > Hi Larry, I’m getting this error: cat /var/log/maillog Mar 25 19:39:56 beastie dovecot: auth: Error: auth: environment corrupt; missing value for DOVECOT_ Mar 25 19:39:56 beastie dovecot: auth: Fatal: unsetenv(RESTRICT_SETUID) failed: Bad address Mar 25 19:39:56 beastie dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs cat /var/log/dovecot-info.log Mar 25 19:39:41 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Mar 25 19:39:41 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Mar 25 19:39:41 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=::1, lip=::1, secured, session= Mar 25 19:39:49 master: Info: Dovecot v2.2.22 (fe789d2) starting up for imap, lmtp Mar 25 19:39:56 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Mar 25 19:39:56 auth: Debug: Wrote new auth token secret to /var/run/dovecot/auth-token-secret.dat Mar 25 19:39:56 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=::1, lip=::1, secured, session= I’m running mariadb100-server-10.0.23, and I tried to recompile every dependencies for dovecot, postfix, mariadb-server without any luck. /Søren

2 4

Re: IMAP Idle
by Joseph Tam 26 Mar '16

26 Mar '16

>> The IDLE disconnection timeout is hardwired in the Dovecot code >> >> http://wiki.dovecot.org/Timeouts >> >> It's set to the RFC minimum of 30min. > > I am ok if connection is closed automatically after 30 min if client is not > responding but connection is not being closed even after 2 days. Hmm. I can't think of why dovecot wouldn't time out. I think maybe the problem is with your webmail system -- it's not detecting when a client connection goes away and releasing all the resources associated with that user. This is not a typical problem though -- most webmail software do not keep persistent IMAP connections open during a session unless they use some IMAP proxy. Are your IMAP connections connected to the webmail server or an IMAP proxy, and is that connection active (despite webmail user disappearing)? Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: VS: Re: Need help solving issue
by MARIA jamieson 26 Mar '16

26 Mar '16

On Saturday, March 26, 2016 2:40 AM, Aki Tuomi <aki.tuomi(a)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(a)yahoo.com> Päivämäärä: 26.3.2016 6.28 (GMT+02:00) Saaja: aki.tuomi(a)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 = </etc/postfix/sslmain.cert ssl_cipher_list = ALL:!LOW:!SSLv2:!SSLV3 ssl_key = </etc/postfix/sslmain.key ssl_protocols = !SSLv3 !SSLv2 userdb { args = /local/etc/dovecot/dovecot-sql.conf driver = sql name = sql } verbose_proctitle = yes verbose_ssl = yes protocol lda { postmaster_address = postmaster(a)mydomain.com sendmail_path = /usr/sbin/sendmail } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_plugins = quota imap_quota } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } local [ipaddress3] { protocol imap { ssl_cert = </etc/postfix/ssl42.cert ssl_key = </etc/postfix/ssl42.key } } local [ipaddress4] { protocol imap { ssl_cert = </etc/postfix/ssl43.crt ssl_key = </etc/postfix/ssl43.pem } }Below is output of postconf -npostconf -n broken_sasl_auth_clients = yes command_directory = /local/sbin config_directory = /local/etc/postfix daemon_directory = /local/libexec/postfix data_directory = /var/db/postfix debug_peer_list = mydomain.com debugger_command = PATH=/bin:/usr/bin:/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 disable_vrfy_command = yes html_directory = /local/share/doc/postfix inet_interfaces = [all my ip addresses here],localhost,127.0.0.1 inet_protocols = all local_recipient_maps = $virtual_mailbox_maps mail_owner = postfix mailq_path = /local/bin/mailq manpage_directory = /local/man mydestination = $myhostname, localhost.$mydomain, localhost, mail.$mydomain, mail2.$mydomain mydomain = localhost myhostname = $mydomain mynetworks = [my own ip addresses here], localhost, 127.0.0.1, localhost.localhost mynetworks_style = host newaliases_path = /local/bin/newaliases proxy_read_maps = $smtpd_sender_login_maps $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps queue_directory = /var/spool/postfix readme_directory = /local/share/doc/postfix sample_directory = /local/etc/postfix sendmail_path = /local/sbin/sendmail setgid_group = maildrop smtp_sasl_auth_enable = yes smtp_sasl_password_maps = proxy:mysql:/local/etc/postfix/mysql_virtual_mailbox_maps.cf smtp_tls_mandatory_protocols = !SSLv2,!SSLv3 smtp_tls_note_starttls_offer = yes smtp_tls_protocols = !SSLv2,!SSLv3 smtp_use_tls = yes smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_non_fqdn_hostname reject_non_fqdn_sender reject_non_fqdn_recipient reject_unauth_pipelining reject_invalid_hostname reject_rbl_client list.dsbl.org reject_rbl_client bl.spamcop.net reject_rbl_client sbl-xbl.spamhaus.org reject_unknown_reverse_client_hostname reject_unknown_client reject_unauth_destination smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_sender_login_maps = proxy:mysql:/local/etc/postfix/mysql_virtual_mailbox_maps.cf smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks smtpd_timeout = 300s smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/postfix/mail.mydomain.crt smtpd_tls_key_file = /etc/ssl/postfix/mail.mydomain.pem smtpd_tls_loglevel = 1 smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3,TLSv1,TLSv1.1,TLSv1.2 smtpd_tls_protocols = !SSLv2,TLSv1,TLSv1.1,!SSLv3,TLSv1.2 smtpd_tls_received_header = yes smtpd_tls_security_level = encrypt smtpd_tls_session_cache_timeout = 3600s soft_bounce = no tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_alias_maps = proxy:mysql:/local/etc/postfix/mysql_virtual_alias_maps.cf virtual_gid_maps = static:125 virtual_mailbox_base = /local/virtual/ virtual_mailbox_domains = proxy:mysql:/local/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 51200000 virtual_mailbox_limit_maps = proxy:mysql:/local/etc/postfix/mysql_virtual_mailbox_limit_maps.cf virtual_mailbox_maps = proxy:mysql:/local/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 125 virtual_transport = virtual virtual_uid_maps = static:125 postconf: warning: /local/etc/postfix/main.cf: unused parameter: smtpd_sasl_password_maps=proxy:mysql:/local/etc/postfix/mysql_virtual_mailbox_maps.cf postconf: warning: /local/etc/postfix/main.cf: unused parameter: anonymousbroken_sasl_auth_clients=yes postconf: warning: /local/etc/postfix/main.cf: unused parameter: virtual_maildir_limit_message="Sorry, this user has overdrawn their diskspace quota. Please try again later." postconf: warning: /local/etc/postfix/main.cf: unused parameter: virtual_mailbox_limit_override=yes postconf: warning: /local/etc/postfix/main.cf: unused parameter: virtual_overquota_bounce=yes postconf: warning: /local/etc/postfix/main.cf: unused parameter: virtual_create_maildirsize=yes postconf: warning: /local/etc/postfix/main.cf: unused parameter: virtual_mailbox_extended=yes On Friday, March 25, 2016 2:41 PM, "aki.tuomi(a)dovecot.fi" <aki.tuomi(a)dovecot.fi> wrote: > On March 25, 2016 at 6:48 PM MARIA jamieson <jamieson.maria(a)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

2 1

Need help solving issue
by MARIA jamieson 26 Mar '16

26 Mar '16

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!

2 2

sieve: filtering based on default destination/folder
by Andrzej A. Filip 26 Mar '16

26 Mar '16

Is it possible to make sieve filter based on default destination/folder? How to trigger special processing/filtering rules when deliver has been executed as 'deliver -m archive ...' ? -- A. Filip

2 3

Re: Reappearing emails - IMAP trace
by Ron Cleven 26 Mar '16

26 Mar '16

>> > >> >A few days back, I sent an overview of this problem, but received no responses. Since then, I have run dozens of traces to isolate the problem, difficult because there are timing issues involved. I have finally nailed it down. If this is not the proper place to report such bugs or if someone knows that this bug has been fixed, please let me know. As I noted in my earlier post, we have been running Dovecot 2.2.10 with a pair of CentOS 7 boxes with replications for the past year. We have been quite happy with the performance and reliability. >> > >> >Recently we received a report that emails could reappear in the INBOX after being deleted. After running a pile of traces, I determined that the problem was strangely related to replications. For the purposes of this discussion, I will refer to the two symmetric replicating servers as A and B. Further, let us assume that during "normal" operation, all the emails are delivered to A via SMTP and are replicated to B. Under those assumptions, if the IMAP user connects to A (where the messages were originally delivered), there is no problem, at least no problem I was able to find. The problem I am describing only arises if the IMAP user connects to B. Connecting to B has never presented any other problems that I am aware of. >> > >> >The test for which I have provided the trace starts with a test mailbox containing only 3 unread messages in the INBOX. Moving 1 of the unread messages to Trash is all that is needed to reproduce the problem. Remember this is ONLY a problem if the IMAP sessions do not connect to the server to which the messages were originally delivered. Also, I found that there is a timing window. The critical IMAP commands are: >> > >> > UID STORE xxx +FLAGS.SILENT (\Seen) >> > UID MOVE xxx Trash >> > >> >If you introduce a large enough delay (I arbitrarily chose 5 seconds) between those two commands, there is no problem. Presumably this has to do with the two boxes syncing up some critical data structure. > What mailbox format do you use? Are you able to reproduce this by running doveadm sync commands manually instead of letting replication do it? For example: > > - doveadm sync -s "" -d -u user@domain > state > - Run the UID STORE & UID MOVE > - doveadm sync -s "`cat state`" -d -u user@domain > > There have been some fixes, especially recentlyhttps://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b… sounds a bit similar although I don't really see how it would apply here. Would be a good idea to try anyway with v2.2.22.rc1 (which seems to be stable enough that I'll make v2.2.22 release soon). > > Anyway, I attempted a few times to reproduce it with your test but wasn't able to. I was out when you were kind enough to reply. To answer your question, we are using Maildir format. The trace I provided was based upon IMAP interactions with Roundcube (though the problem was reproducable with several mail clients). I left in a few more steps to make the trace look less contrived. However, I reduced it further to just a couple of connection sessions. What I found in that exercise that was not apparent to me in my prior posting was that the "STATUS INBOX" command that ultimately reveals the problem (it shows the message reappearing) only becomes "wrong" when it is done in a subsequent session. That is, even if I inject an artificially large delay after the "UID STORE" / "UID MOVE" commands before the "STATUS INBOX" command in the same session, that result is never "wrong". But, as soon as I open a subsequent IMAP session, the "STATUS INBOX" command then shows the problematic results. I have never dug into the Dovecot code base, but I assume this relates to how the session data is cached and how the replications update it. None of this is relevant if the problem has already been fixed, so I will endeavor to set up a couple of test boxes with the current version to verify. The link you provided does look quite hopeful. Thanks so much.

1 0

Re: IMAP Idle
by Joseph Tam 26 Mar '16

26 Mar '16

Joy <pj.netfilter(a)gmail.com> wrote: > We have implement imap idle in web mail built by us to have > push mail feature. IMAP idle working perfectly with browser notification > and we are happy with it but having one issue with users who close the > browser directly and never logout in that case there are number of idle > connection which are not in use and users are unable to login once IP wise > connection limit is reached. > > Dovecot is not closing connection which are not in use, is there any > setting available which can help me to resolve this issue. I had much the same situation where a user signed up with a roaming wireless carrier that assigned a new IP to the client whenever it got passed from one access point to another. Good fun when this person took a bus ride through the city, leaving orphaned connections in its wake. The IDLE disconnection timeout is hardwired in the Dovecot code http://wiki.dovecot.org/Timeouts It's set to the RFC minimum of 30min. You'll have to recompile Dovecot to lower this to a non-RFC compliant value. I'm not sure how this this will affect clients, but 30min seems to be overly generous. Joseph Tam <jtam.home(a)gmail.com>

2 1

NetApp NFS vs. ZFS and NFS for Maildir
by Alessio Cecchi 26 Mar '16

26 Mar '16

Hi, I'm evaluating to switch from NetApp to a ZFS appliance (like Qsan). Our setup is Dovecot, Maildir for email storage and NFS to share mailboxes (more than 30k users) across POP/IMAP and MX servers. NetApp NFS works fine also under high load but have some limitation for inode numbers per Volume and is expensive (but recently their prices have dropped). ZFS, I read, suggest to create many small Raid Group to increase IOPS, but this configuration (N Raid instead of one RAID-DP like NetApp) is more complex to manage, or not? Someone has experiences with ZFS and NFS(v3) in high load environments? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

6 16

State for dsync not working.
by Simon Pierre Desrosiers 26 Mar '16

26 Mar '16

Hello, Since replication does not seem to work on Mac OSX, I will run doveadm sync by hand every few minutes. In order to improve efficiency, I would like to use state. I have tried a few ways, but I always get the following error doveadm(user): Error: Saved sync state is invalid, falling back to full sync: Invalid base64 data KBtMOd0181bQ/wAAoQsxE90181YBAAAAAQAAAAAAAAAAAAAAAAAAABtI+mg= Here is the code I use to sync : for user in $userlist ; do doveadm sync -u $user -s "/Users/_dovecot/.bin/syncStates/syncstate$user" tcp:xxx.xxx.xxx.xxx > "/Users/_dovecot/.bin/syncStates/syncstate$user" done Any idea on how I can correct the encoding error ? Thank you

1 0

Dovecot on FreeBSD 10.1
by Søren Andersen 25 Mar '16

25 Mar '16

I'm experiencing the same problem as mentioned earlier in the mailing list. - Is there some kind of workaround for this issue? http://dovecot.org/pipermail/dovecot/2015-April/100549.html /Søren

2 3