- dovecot - dovecot.org

[Dovecot] Random LDA failure to access auth socket
by Chris Richards 19 Mar '13

19 Mar '13

Greetings all. Please forgive me if I'm posting something that has already been addressed, but my google-foo is not strong enough to find the solution. I've got a dovecot server running version 2.0.19 on Gentoo Hardened. I have Postfix as my MTA, and it is calling the Dovecot LDA to deliver the mail. Everything is working great, mail is being delivered, and the users are happy. However, I am noticing that I have random entries like this: Mar 1 20:19:23 hermes dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=97(dovecot) egid=97(dovecot) missing +r perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) Mar 1 20:19:23 hermes dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. Since these messages came from the server log, looking in the server log for more information is rather pointless. I have 10-master.conf configured as follows: service auth { unix_listener auth-userdb { mode = 0600 user = vmail group = vmail } In 15-lda.conf I have: protocol lda { mail_plugins = $mail_plugins sieve quota } In Postfix master.cf, I have the following: dovecot unix - n n - - pipe flags=DRhu user=vmail:users argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${user}@${nexthop} Permissions on the socket are: srw------- 1 vmail vmail 0 Feb 24 23:43 auth-userdb Judging from the log, my problem is that the LDA appears to be trying to access the socket as the dovecot user (rather than the vmail user), but my question is why? What logging can I use to tell me if postfix is calling with the wrong permissions or if the lda is somehow getting confused? Any help or suggestions greatly appreciated. Thanks, Gizmo

2 6

[Dovecot] SASL + Postfix woes
by Jerry 18 Mar '13

18 Mar '13

Okay, I wasn't going to try and fix up the messed up mail server I was given; however, I decided that I might as well try. Situation: The system has a Postfix MTA and uses Dovecot for LDA and Cyrus-SASL for SASL. That works fine. I decided that I wanted to switch over to Dovecot for SASL. dovecot is presently using MySQL for its database. I make the (I thought) necessary changes in Postfix and restarted it. Big problem. SASL is now broken. I turned on logging in Dovecot to see what was happening, but apparently nothing is happening. There are no entries regarding Postfix attempting to negotiate an SASL request with Dovecot. This is the "dovecot -n" outout (yes, I know it is an old version) # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.3-STABLE amd64 ufs log_path: /var/log/dovecot.log login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/mail/vhost/seibercom.net/gerard mail_plugins: expire imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: postmaster_address: postmaster(a)seibercom.net mail_plugins: sieve sieve_global_path: /usr/local/etc/dovecot/sieve/gerard.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: expire: Trash 2 Spam/* 2 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf This is the "dovecot-sql.conf" file: driver = mysql connect = host=localhost dbname=Dovecot user=root password=xxxxxxxx password_query = SELECT concat(userid, '@', domain) AS user, password \ FROM users WHERE userid = '%n' AND domain = '%d' user_query = SELECT uid, gid, home FROM users WHERE userid = '%n' AND domain = '%d' This is the pertinent part of the postconf -fn output: broken_sasl_auth_clients = yes smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/usr/local/etc/postfix/sasl_password_maps smtp_sasl_security_options = noanonymous smtp_sasl_type = dovecot smtpd_client_restrictions = reject_unauth_pipelining permit_sasl_authenticated smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $mydomain smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous I have tried using "dovecot" in place of "private/auth", but it doesn't make any difference. This is the only output from the postfix maillog: Mar 18 08:13:02 scorpio postfix/smtpd[65217]: connect from localhost[127.0.0.1] Mar 18 08:13:02 scorpio postfix/smtpd[65217]: warning: localhost[127.0.0.1]: SASL CRAM-MD5 authentication failed: authentication failure Mar 18 08:13:02 scorpio postfix/smtpd[65217]: lost connection after AUTH from localhost[127.0.0.1] Again, it doesn't appear that Postfix ever actually makes contact with Dovecot. I am probably doing something extremely stupid, but I just cannot figure out what it is. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________

2 2

[Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
by Alex 18 Mar '13

18 Mar '13

Hi, I have an fc18 system with postfix and dovecot-2.1.13 and have configured them to use sasl for SMTP Auth and Maildir with imaps. The system is running now, so I'm trying to set up thunderbird to autodetect all settings during the initial account setup. However, it seems to want to use port 143 and STARTTLS, and not port 993, which is what I would expect. When I force it to use 993, I receive a certificate failure message: Mar 12 23:20:45 propnew postfix/submission/smtpd[14423]: initializing the server-side TLS engine Mar 12 23:20:45 propnew postfix/tlsmgr[14425]: open smtpd TLS cache btree:/var/lib/postfix/smtpd_tls_session_cache Mar 12 23:20:45 propnew postfix/tlsmgr[14425]: tlsmgr_cache_run_event: start TLS smtpd session cache cleanup Mar 12 23:20:45 propnew postfix/submission/smtpd[14423]: connect from unknown[192.168.1.43] Mar 12 23:20:45 propnew dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=192.168.1.43, lip=66.111.222.101, TLS: SSL_read() failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate: SSL alert number 42, session=<BGBS5MXXhQDAqAEr> Mar 12 23:20:45 propnew postfix/submission/smtpd[14423]: lost connection after CONNECT from unknown[192.168.1.43] These are self-signed certs created using dovecot's mkcert.sh script. Is this a problem with the cert or with the dovecot configuration? Is it conventional to use port 143 for encrypted IMAP connections these days, and not just 993? I'm finding that port 25 works with TLS and postfix now too, not just port 587, so I'm really confused. I've included my doveconf output below. I'd appreciate it if someone could review it for me to be sure. # 2.1.13: /etc/dovecot/dovecot.conf # OS: Linux 3.8.1-201.fc18.x86_64 x86_64 Fedora release 18 (Spherical Cow) ext4 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = maildir:/home/%u/Maildir 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 ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_min_avail = 20 service_count = 0 } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { driver = passwd } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Thanks, Alex

9 18

Re: [Dovecot] Dovecot - Sieve script loaded but filtering doesn't works ?
by Clement PAULET 18 Mar '13

18 Mar '13

Hello Steffen, Thanks for your reply, This is my script (using for my test) : require "fileinto"; if address "To" "info(a)info.xx.com" { fileinto "Test"; } Clement ------------------------------ Message: 7 Date: Mon, 18 Mar 2013 13:23:33 +0100 (CET) From: Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: [Dovecot] Dovecot - Sieve script loaded but filtering doesn't works ? Message-ID: <alpine.DEB.2.02.1303181322430.3303(a)pc-2m63.inf.fh-bonn-rhein-sieg.de> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Mar 2013, Clement PAULET wrote: When I use a Sieve script, it 's loaded but actions are not respect with this logs : The sieve script just trying to redirect to INBOX.Test folder but doesn't works.. First of all, how does your script looks like? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUUcHRl3r2wJMiz2NAQKoswf/WczI0q9k0WqWzRPr7lwuBEeiQQlYBDaq Lap8YNnbxDsczxgYZ/i0gDrq7f612A0nKWHBC806DxH4dHNyUwBPYVqFAT7edvk4 ns99f4bNh6GsufC1CY5tY/1DjT5ykEzkTmaV443YH50jQ4iPnDohOMsBBRlhoWN4 8KCLCNafCYXf48QjnAfoLt4TjaxyYb//7otYJN2CqLOGbvWoJwrpNgmuhvST+PNm RQXLG1lpxzt7QMP++fTMXa6A/SwVsglhAUS6xFdAuoOBsx1jPtvA+mot9gqpi02I j2WquMsycviWprYD2FsET903TWU/5+boxg2UBOettsTqhfwABkIcvQ== =ygun -----END PGP SIGNATURE-----

2 1

[Dovecot] Dovecot not obeying disable_plaintext_auth = yes and how to force/disable encryption
by Darren Pilgrim 18 Mar '13

18 Mar '13

I'm using Dovecot 2.1.15. I need to require encryption and only secure auth on public addresses, but allow plaintext auth over an unencrypted connection on localhost. I have so far (excerpts from `doveconf -a`): auth_mechanisms = cram-md5 plain disable_plaintext_auth = yes listen = service imap-login { inet_listener imap-local { address = ::1 port = 143 ssl = no } inet_listener imap-pub { address = 2001:db8::1 port = 993 ssl = yes } } service managesieve-login { inet_listener sieve-local { address = ::1 port = 4190 ssl = no } inet_listener sieve-pub { address = 2001:db8::1 port = 4190 ssl = no } } The ssl option only seems to switch the inet_listener between using a secure socket and using STARTTLS. How do I tell a given inet_listener to do neither? How do I tell a given inet_listener to require STARTTLS before allowing AUTH/SASL? I would prefer to offer only CRAM-MD5 on the UGA/public ports, and only PLAIN or at least also PLAIN on localhost. I tried adding auth_mechanisms lines to each inet_listener block, but got parse errors. How do I do this? Dovecot seems to ignore disable_plaintext_auth = yes: # telnet 2001:db8::1 4190 Trying 2001:db8::1... Connected to host.example.com. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave" "NOTIFY" "mailto" "SASL" "CRAM-MD5 PLAIN" "STARTTLS" "VERSION" "1.0" OK "Dovecot ready." -- Please reply on list.

1 1

[Dovecot] Dovecot as LDA with Postfix and virtual users
by Christian Benke 17 Mar '13

17 Mar '13

Hello! I've been trying to configure Dovecot to work as LDA for file-based virtual users with Postfix. Some part in the configuration seems to miss though, as mails are received by Postfix, but instead of giving it to Dovecot for delivery, it delivers the mails itself. Postfix drops the mail in /var/mail/<user>/mbox, if Dovecot would be called, it should deliver it to /var/vmail/<domain>/<user>/Maildir. I've made sure to add the dovecot-service to postfix/master.cf according to http://wiki2.dovecot.org/LDA/Postfix and tried all kinds of settings and did quadruple checks for errors. I'm using Debian 6.0 with Dovecot 2.1.7(From backports) and Postfix 2.7.1 I've been trying to figure out what's missing for a few hours now and have to give up for today. I hope someone can help me with a hint what's missing or wrong :-/ Here's an excerpt from my mail.log, my postconf -n and dovecot -n: Mar 17 00:02:46 poab postfix/smtpd[15333]: connect from mail-wg0-f47.google.com[74.125.82.47] Mar 17 00:02:46 poab postfix/smtpd[15333]: setting up TLS connection from mail-wg0-f47.google.com[74.125.82.47] Mar 17 00:02:46 poab postfix/smtpd[15333]: Anonymous TLS connection established from mail-wg0-f47.google.com[74.125.82.47]: TLSv1 with cipher RC4-SHA (128/128 bits) Mar 17 00:02:46 poab dovecot: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Mar 17 00:02:46 poab dovecot: auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Mar 17 00:02:46 poab dovecot: auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_pgsql.so Mar 17 00:02:46 poab dovecot: auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_sqlite.so Mar 17 00:02:46 poab dovecot: auth: Debug: passwd-file /etc/dovecot/users: Read 1 users in 0 secs Mar 17 00:02:46 poab dovecot: auth: Debug: auth client connected (pid=0) Mar 17 00:02:46 poab postfix/smtpd[15333]: 66AD04E23EE: client=mail-wg0-f47.google.com[74.125.82.47] Mar 17 00:02:46 poab postfix/cleanup[15340]: 66AD04E23EE: message-id=<CAAMQ8bSEetcSYKKHKhbAqWxJwRewaPB_wA2DK8J4N-q5Y+dG7w(a)mail.gmail.com> Mar 17 00:02:46 poab postfix/qmgr[14844]: 66AD04E23EE: from=<benkkk AT wheemail.com>, size=1611, nrcpt=1 (queue active) Mar 17 00:02:46 poab postfix/smtpd[15333]: disconnect from mail-wg0-f47.google.com[74.125.82.47] Mar 17 00:02:46 poab postfix/local[15341]: 66AD04E23EE: to=<benkkk AT example.com>, relay=local, delay=0.35, delays=0.3/0.01/0/0.04, dsn=2.0.0, status=sent (delivered to mailbox) Mar 17 00:02:46 poab postfix/qmgr[14844]: 66AD04E23EE: removed # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix debug_peer_level = 3 inet_interfaces = all inet_protocols = all mailbox_size_limit = 5120000000 myhostname = example.com mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + relayhost = smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt smtp_tls_note_starttls_offer = yes smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_helo_required = yes smtpd_helo_restrictions = reject_invalid_helo_hostname smtpd_recipient_restrictions = reject_unknown_recipient_domain, reject_unauth_pipelining, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_reject_unlisted_recipient = yes smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_tls_security_options = $smtpd_sasl_security_options smtpd_sasl_type = dovecot smtpd_sender_login_maps = hash:/etc/postfix/sender_login_maps smtpd_sender_restrictions = reject_authenticated_sender_login_mismatch smtpd_tls_CAfile = /etc/ssl/certs/ca-certificates.crt smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/certs/postfix.pem smtpd_tls_key_file = /etc/ssl/private/postfix.key smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes tls_random_source = dev:/dev/urandom virtual_alias_maps = hash:/etc/postfix/virtual_alias_maps virtual_mailbox_domains = hash:/etc/postfix/virtual_mailbox_domains virtual_mailbox_maps = hash:/etc/postfix/virtual_mailbox_maps virtual_transport = dovecot # dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-openvz-amd64 x86_64 Debian 6.0.7 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-master auth_verbose = yes auth_verbose_passwords = sha1 first_valid_gid = 5000 first_valid_uid = 5000 last_valid_gid = 5000 last_valid_uid = 5000 lda_mailbox_autocreate = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_gid = 5000 mail_home = /var/vmail/%d/%n mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = 5000 namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=SHA1 /etc/dovecot/users driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 0 } } ssl_cert = </etc/ssl/certs/postfix.pem ssl_key = </etc/ssl/private/postfix.key userdb { args = uid=5000 gid=5000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } verbose_ssl = yes protocol lda { mail_plugins = } Thanks & good night, Christian -- Central Asia by bike, starting May 2013 - http://poab.org

2 4

[Dovecot] Dovecot SASL & Postfix
by Jerry 17 Mar '13

17 Mar '13

This is probably a dumb question, but I'll ask anyway. I am currently using Postfix with Dovecot and Cyrus-SASL. I want to switch over to Dovecot SASL. The regular Dovecot user/password file is not the same as the file used by cyrus-sasl. Usewr names and passwords are different. I created a flat file that dovecot can use for SASL look-ups; however, exactly where in the Dovecot config file to I place the entry. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________

3 5

[Dovecot] Connection to PGSQL fails?
by Bjørn T Johansen 17 Mar '13

17 Mar '13

I have configured a new server and copied the dovecot-sql.conf file that works a different server to the new server... But when Dovecot tries to connect to the database, the following error appears..: Mar 16 22:28:25 smtp dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Mar 16 22:28:25 smtp dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Mar 16 22:28:25 smtp dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so Mar 16 22:28:25 smtp dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Mar 16 22:28:25 smtp dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so Mar 16 22:28:25 smtp dovecot: auth: Error: pgsql: Connect failed to serviceadmin: could not connect to server: Permission denied Mar 16 22:28:25 smtp dovecot: auth: Error: #011Is the server running on host "10.50.150.35" and accepting Mar 16 22:28:25 smtp dovecot: auth: Error: #011TCP/IP connections on port 5432? Mar 16 22:28:25 smtp dovecot: auth: Debug: auth client connected (pid=1768) But if I use psql and connects to the same db server with the same username and password, I can successfully connect... What am I missing? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

3 7

[Dovecot] sieve: seconds-extension for vacation
by Peer Heinlein 16 Mar '13

16 Mar '13

Hi, looks like Dovecot-Sieve doesn't know the seconds-extension for vacation: main script: line 5: error: unknown tagged argument ':seconds' for the vacation command (reported only once at first occurence). main script: error: validation failed. http://tools.ietf.org/html/rfc6131 Could this be added during the next releases? Regards, Peer -- Treffen Sie uns auf den Chemnitzer Linux-Tagen vom 16. bis 17. März 2013! Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

3 2

[Dovecot] Dovecot error wuth MySQL
by Cesar 16 Mar '13

16 Mar '13

Hello PeopleCan anybody help me?My scenario:- One computer with:a) postfix-2.6.6-2.2.el6_1.x86_64b) mysql-5.1.66-2.el6_3.x86_64c) dovecot-2.0.9-2.el6_1.1.x86_64d) dovecot-mysql-2.0.9-2.el6_1.1.x86_64Postfix and Dovecot auth over MySQLThe Problem:- logwatch show me: Dovecot disconnects: auth failed, 1 attempts: 1 Time(s) in IDLE: 2 Time(s) no auth attempts: 6 Time(s) no reason: 6 Time(s) **Unmatched Entries** dovecot: auth: Error: mysql: Query failed, retrying: MySQL server has gone away: 125 Time(s)(125 Times Wow)For example part of maillog show me:About MySQL auth failed:Mar 10 03:55:05 gateway dovecot: auth: Error: mysql: Query failed, retrying: MySQL server has gone awayMar 10 03:55:05 gateway dovecot: auth: mysql: Connected to localhost (mail)Mar 10 03:55:05 gateway dovecot: pop3-login: Login: user=user-name(a)domain.com>, method=PLAIN, rip=192.168.100.31, lip=190.128.232.2, mpid=16352Mar 10 03:55:05 gateway dovecot: pop3(user-name(a)domain.com): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0The Question:How to fix it? (i don't want to see the dovecot auth error mysql)I will be very grateful to anyone who can help me ----- Best Regards Cesar -- View this message in context: http://dovecot.2317879.n4.nabble.com/Dovecot-error-wuth-MySQL-tp40765.html Sent from the Dovecot mailing list archive at Nabble.com.

5 6