similar to: Error message in logs since 1.1.6 upgrade

Hi, first of all, many thanks for a great piece of software. Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions). After the update I now see randomly the following errors in the log file on my first proxy: ... Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL

Hi, I've just started trying allow_nets on one of my servers. I have auth_debug and auth_verbose both enabled and the output is as follows: Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network 127.0.0.1/8 Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network

What kind of test are you running? Aki > On April 27, 2017 at 12:00 PM Poliman - Serwis <serwis at poliman.pl> wrote: > > > I turned of ssl_cipher_list in dovecot.conf file (so it's default) but test > still gives errors: > Apr 27 08:55:06 serwer-1 dovecot: pop3-login: Error: SSL: Stacked error: > error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown

Cipher list which You post provide better compatibility or security than those which I currently have? On older software version these cipher list works well and not generate any errors when I run Internal PCI scan test from https://cloud.tenable.com for another server. But for new server with newer software during test I got errors in mail.err. 2017-04-27 10:00 GMT+02:00 Aki Tuomi <aki.tuomi

Hi, Sorry to bother, I don't know if this mailing list is the right place to look for help setting up dovecot.. Anyway I've got standard IMAP working fine, and I used mkcert.sh after editing the openssl config, and it seemed to work properly (I had to change some directories, I am using the FreeBSD 5.1-CURRENT port).. Anyway, when I try to connect using Outlook, here is what the log

I've got dovecot working on imap But when I try to run imaps I get: imap-login: Nove 08 19:11:19 Warning: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [192.168.1.103] Now I'm not sure if theres any difference here, but I don't have string for 'login = imaps' or 'login = pop3s' to match with my protocols string

Hi, To default dovecot.conf file I added (based on found documentation): ssl = required disable_plaintext_auth = yes #change default 'no' to 'yes' ssl_prefer_server_ciphers = yes ssl_options = no_compression ssl_dh_parameters_length = 2048 ssl_cipher_list =

I turned of ssl_cipher_list in dovecot.conf file (so it's default) but test still gives errors: Apr 27 08:55:06 serwer-1 dovecot: pop3-login: Error: SSL: Stacked error: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol Apr 27 08:55:06 serwer-1 dovecot: pop3-login: Error: SSL: Stacked error: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol Apr 27 08:55:07

Internal PCI Scan on Tenable.io website. Of course after register account. 2017-04-30 9:11 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > What kind of test are you running? > > Aki > > > On April 27, 2017 at 12:00 PM Poliman - Serwis <serwis at poliman.pl> > wrote: > > > > > > I turned of ssl_cipher_list in dovecot.conf file (so it's

hi list, first of all, many thanks to the developers of dovecot for this great piece of software! i'm running dovecot 0.99.9.1 on netbsd-current - runs very fine until i try to use sylpheed from my client to connect via ssl: --snip-- Jun 13 08:48:32 devbox imap-login: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [192.168.100.88] Jun 13

Hi! It seems there are problem with POP3 connection when TLS enabled. Previously it worked fine, but for now it doesn't... Plain & SSL POP3 works. Plain, TLS & SSL IMAP works too. In logs nothing than: dovecot: Aug 16 10:36:23 Warning: pop3-login: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [xxx.xxx.xxx.xx] xxx.. - remote ip

I disabled postscreen and enabled logging, I have all ports working except 993, in log when I try to connect on port 993 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=10.244.0.24, lip=10.244.0.108, TLS handshaking: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number, session=<rEH6ocGoOtUK9AAY> I found that I could

hi, I'm just download the latest cvs and try to use imaps. in mozilla I've got the following message window: ----------------------------- mail.int.bppiac.hu received a message with incorrect Message Authentication Code. If the error occurs frequently, contact the website administrator. ----------------------------- and there is only one OK button:-) and this happens always. what can be

Hi Timo, Was getting the following error repeatedly in my mail client (squirremail) "error: connection dropped by IMAP server" Looked at the logs for this user and found the following: Nov 19 17:11:32 mink dovecot: IMAP(bobuser at maildom.com): broken sync positions in index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot:

Thank You for answers. But: 1. How should be properly configured ssl_cipher_list? 2. Ok, removed !TLSv1 !TLSv1.1. 3. Strange thing with ssl_protocols and ssl_cipher_list, because on older server on Ubuntu 14.04 LTS, dovecot 2.2.9 and postfix 2.11.0 these two lines looks exactly this same and no errors in mail.err file and mailes works without any problem. 4. No, currently I don't use LMTP.

http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP

http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP

Hello everyone, I've been asked by a colleague to have a look at some extremely weird dovecot SSL issue they are seeing on one of the student mailservers. They are running dovecot 1.1.6 (yes, I know, a bit old ...) on SLES 10.2 x86_64 with imap(+starttls), imaps, pop3(+starttls) and pop3s enabled. Every couple of weeks the pop3s and pop3+starttls part bail out out. Clients can't connect,

Hi, I'm getting a lot of the following messages in my mail.err log. Jul 12 11:25:51 mink dovecot: IMAP(user1 at domain1.net): Corrupted transaction log file /virtual/store1/mail/u/user1_domain1.net/Maildir/.Sent/dovecot.index.log: Append with UID 925, but next_uid = 926 Jul 12 12:44:56 mink dovecot: IMAP(user2 at domain1.net): Corrupted transaction log file

Hi, I'm using postfix with Dovecot 1.0.5 and getting the following errors when a user moves a massive folders contents to trash (65000 or so messages): Apr 21 15:31:01 mink dovecot: IMAP(dev2 at aluminati.net): Timeout while waiting for lock for transaction log file /virtual/store1/mail/d/dev2_aluminati.net/Maildir/.Deleted Items/dovecot.index.log Is there anything I can do to compensate for