similar to: openssl decryption failed

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

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 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

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 got two imap boxes, one is running 1.1.5 and hasn't exhibited the error below, but the one that's been upgraded to 1.1.6 is showing them. Nov 14 16:06:31 mink dovecot: imap-login: Disconnected (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS handshaking: SSL_accept() failed: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac If this isn't

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

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

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,

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

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz.sig I tried to keep the configuration and APIs compatible with v2.0.beta1, but unfortunately there were a few things that really had to be changed: 1. passdbs and userdbs have now a separate "driver" setting inside them. So for example if you had: userdb passwd {

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta2.tar.gz.sig I tried to keep the configuration and APIs compatible with v2.0.beta1, but unfortunately there were a few things that really had to be changed: 1. passdbs and userdbs have now a separate "driver" setting inside them. So for example if you had: userdb passwd {

Am 23.06.2020 um 07:33 schrieb Bernardo Reino: > If you use postfix a "workaround" is to temporarily disable postscreen, > which IIRC is the one (rightly) complaining about the improper pipelining. > > Cheers, > Bernardo Reino No, submitting on SMTP port 25 would be the wrong step. There's submission on port 587 or submissions (formerly called smtps) on port 465

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, 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 run dovecot --version 2.3.10.1 (a3d0e1171) postconf mail_version mail_version = 3.5.7 with three valid accounts on the server, user1 at example1.net user2 at example2.net admin at mx.example.com I can send/receive from each -- both to/from external addresses, as well as between one another. E.g., on mail sent to user2 at example2.net -> admin at mx.example.com logs of the

Dear very helpful friends, It is Sunday, there is no air traffic in Europe, what better to do than try and learn me some more R. I have the following example: owner <- c(1:4) animal <- c("cat", "dog", "cat", "dog") char.1 <- c("fluffy", "playful", "mean", "stupid") food <- c("cat food",

Dovecot Users, I have a sudden new problem that has cropped up just recently and I am stumped. My implementation has been working for over a year with no issues. Version Data: Dovecot: v2.2.10 (using self signed certificates) openSSL: v1.01e Gmail Android App: v6.10.23 November 3, 2016 The issue: I use the iphone Gmail App to access my e-mail from phone and tablet. It is simple and supports

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.