SSL connection reset by peer
Hi,
I am running a dovecot server and have set up an external monitoring,
where every five minutes a login with SSL on port 993 is done. I usually
get once a day an error "connection reset by peer - SSL connect", which
goes away until the next monitor is executed.
Initially I thought that raising the mail_max_userip_connections in
protocol imap in 20-imap.conf to 256 should do the trick - but the error
stays.
What could be the reason for this error and which configuration values
could be changed in order to avoid this error?
I read a lot of different suggestions - but did not find a plausible
explanation and recommendation.
Thanks in advance!
--
Cheers,\\|//
Vince (o o)
ooO-(_)-Ooo-
''' (o)_(o)[ ][0][ ]
ô¿ô (=°o°=) World Domination by Copy and Paste [ ][ ][0]
-(")_(")[0][0][0]
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Ooo.
---.ooO( )-
( )(_/
\_)
Re: Replication sieve scripts.
Op 21-7-2016 om 15:50 schreef Luescher Claude: Hello, Thanks for the advice. I have looked for the libs and here is the difference: [...] First problem I notice is this /home/vmail/company.com/us...@company.com//.dovecot.sieve missing. Is this supposed to be a file or a directory? The second sieve_global_dir, I don't need global rules. The third is this minus gid=-1 value. The user/group/rights on that directory is not different from the mail dirs (where the replication works): ls -al /home/vmail/company.com/us...@company.com//sieve drwx--S--- 2 vmail vmail 4096 Jul 21 15:17 tmp The important directory for me is the siev_after because roundcube vacation plugin puts the sieves in there for example: -rw--- 1 vmail vmail 413 Jul 21 15:23 01_vacation.sieve -rw--- 1 vmail vmail 124 Jul 21 15:23 01_vacation.svbin -rw-r--r-- 1 vmail vmail 193 Feb 26 2014 antispam.sieve -rw-r--r-- 1 vmail vmail 272 Apr 13 2015 antispam.svbin Gets created after setting out of office message but will not get replicated to the other node. As I have showed in my earlier doveconf output is defined: sieve = ~/.dovecot.sieve sieve_after = ~/sieve_after sieve_dir = ~/sieve sieve_duplicate_period = 1h sieve_extensions = +editheader sieve_max_redirects = 20 And the sieve scripts work locally per server they are just not replicating as they should be. There is your problem. The sieve_after/sieve_before settings usually point to administrator-controlled global scripts. Therefore, these are not replicated by the doveadm_sieve plugin. Only the user's scripts in the ~/sieve directory and the active script marked by ~/.dovecot.sieve (symlink) are replicated. Regards, Stephan.
Suggested improvement for antispam plugin documentation
Hello,
I struggled a bit with getting the antispam plugin to work, because the
plugin configuration in http://wiki2.dovecot.org/Plugins/Antispam is
incomplete. After some twiddling, I ended up with this:
# /etc/dovecot/conf.d/90-plugin.conf
plugin {
antispam_backend = mailtrain
antispam_mail_spam = spam
antispam_mail_notspam = ham
antispam_mail_sendmail = /path/to/mailtrain/script
antispam_spam = Junk;Spam
antispam_trash = Deleted Messages;Trash
}
I know that the antispam plugin has not yet been officially released,
but I think it might be worth updating the documentation anyway. Your
thoughts?
-Ralph
Re: Replication sieve scripts.
Hello, Thanks for the advice. I have looked for the libs and here is the difference: Dovecot production env 2.2.10: /usr/lib/dovecot/modules/doveadm rw-r--r-- 1 root root 18560 Jan 9 2014 lib10_doveadm_acl_plugin.so -rw-r--r-- 1 root root 14256 Jan 9 2014 lib10_doveadm_expire_plugin.so -rw-r--r-- 1 root root 10232 Jan 9 2014 lib10_doveadm_quota_plugin.so -rw-r--r-- 1 root root 51352 Jan 9 2014 lib10_doveadm_sieve_plugin.so -rw-r--r-- 1 root root 14344 Jan 9 2014 lib20_doveadm_fts_plugin.so Dovecot new test env: /usr/dovecot/lib/dovecot/doveadm -rw-r--r-- 1 root root 140574 Jul 20 12:53 lib10_doveadm_acl_plugin.a -rwxr-xr-x 1 root root 1066 Jul 20 12:53 lib10_doveadm_acl_plugin.la -rwxr-xr-x 1 root root 98910 Jul 20 12:53 lib10_doveadm_acl_plugin.so -rw-r--r-- 1 root root 56108 Jul 20 12:53 lib10_doveadm_expire_plugin.a -rwxr-xr-x 1 root root 1087 Jul 20 12:53 lib10_doveadm_expire_plugin.la -rwxr-xr-x 1 root root 43879 Jul 20 12:53 lib10_doveadm_expire_plugin.so -rw-r--r-- 1 root root 97212 Jul 20 12:53 lib10_doveadm_quota_plugin.a -rwxr-xr-x 1 root root 1080 Jul 20 12:53 lib10_doveadm_quota_plugin.la -rwxr-xr-x 1 root root 63227 Jul 20 12:53 lib10_doveadm_quota_plugin.so -rw-r--r-- 1 root root 338560 Jul 20 12:53 lib10_doveadm_sieve_plugin.a -rwxr-xr-x 1 root root 1286 Jul 20 12:53 lib10_doveadm_sieve_plugin.la -rwxr-xr-x 1 root root 177604 Jul 20 12:53 lib10_doveadm_sieve_plugin.so -rw-r--r-- 1 root root 139748 Jul 20 12:53 lib20_doveadm_fts_plugin.a -rwxr-xr-x 1 root root 1066 Jul 20 12:53 lib20_doveadm_fts_plugin.la -rwxr-xr-x 1 root root 94615 Jul 20 12:53 lib20_doveadm_fts_plugin.so Also I have set the mail_log to debug as you have suggested and I see the following for users in the logs (with my "old" version): Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: doveadm-sieve: Iterating Sieve mailbox attributes Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: sieve: Pigeonhole version 0.4.2 initializing Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: sieve-storage: using active sieve script path: /home/vmail/company.com/us...@company.com//.dovecot.sieve Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: sieve-storage: using sieve script storage directory: /home/vmail/company.com/us...@company.com//sieve Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: sieve-storage: using permissions from /home/vmail/company.com/us...@company.com//sieve: mode=0700 gid=-1 Jul 21 11:52:27 server1 dovecot: dsync-server(us...@company.com): Debug: sieve-storage: relative path to sieve storage in active link: sieve/ Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: doveadm-sieve: Iterating Sieve mailbox attributes Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve: Pigeonhole version 0.4.2 initializing Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve-storage: using active sieve script path: /home/vmail/company.com/us...@company.com//.dovecot.sieve Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve-storage: using sieve script storage directory: /home/vmail/company.com/us...@company.com//sieve Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve-storage: using permissions from /home/vmail/company.com/us...@company.com//sieve: mode=0700 gid=-1 Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve-storage: relative path to sieve storage in active link: sieve/ Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: doveadm-sieve: Iterating Sieve mailbox attributes Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve: Pigeonhole version 0.4.2 initializing Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 21 15:17:21 server1 dovecot: dsync-local(us...@company.com): Debug: sieve-storage: using active sieve script path: /home/vmail/company.com/us...@company.com//.dovecot.sieve First problem I notice is this /home/vmail/company.com/us...@company.com//.dovecot.sieve missing. Is this supposed to be a file or a directory? The second sieve_global_dir, I don't need global rules. The third is this minus gid=-1 value. The user/group/rights on that directory is not different from the mail dirs (where the replication works): ls -al
Re: an e-mail client for dovecot ?
On 19/07/16 16:42, Miquel van Smoorenburg wrote: Known problem. Sort of a indexing thundering herd problem. Preferences -> Advanced -> Config Editor, set mail.db.idlelimit to a large number. I set it to 3000. Fixed it for me.. Mike. If you're using a Thunderbird version > 38 then you don't need to make this change, it is to do with reducing auto closing mail folders and opening them again (which is CPU intensive). If you are using a version > 38 then you should retain the default value to mail.db.idle_limit. smime.p7s Description: S/MIME Cryptographic Signature
