similar to: [Fwd: Re: Upgrade to 2.3.1 has failed]

Displaying 20 results from an estimated 4000 matches similar to: "[Fwd: Re: Upgrade to 2.3.1 has failed]"

2018 Dec 14
2
Upgrade to 2.3.1 has failed
Aki hello, thank you. Hopefully excerpts and top posting are acceptable in the mailing list?? On that assumption: Thanks for the input. I've checked out your suggestions (details below) but unfortunately no joy. I also restored my backup 10-ssl.conf. It indeed has the "<" sign with a space before the explicit paths to the files: ? ? ssl_cert =
2018 Dec 14
0
Upgrade to 2.3.1 has failed
> On 14 December 2018 at 02:12 "C. Andrews Lavarre" <alavarre at gmail.com> wrote: > > > Problem: > We had Dovecot v2.2 working just fine under openSUSE Leap 42.3. But we > upgraded openSUSE to Leap 15.0. > In the process, Dovecot got upgraded from 2.2 to 2.3.1. It no longer > works and I haven't figured out how to downgrade to the older working >
2018 Dec 15
0
Upgrade to 2.3.1 has failed
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> That command is missing -starttls imap? or are you using port 993? </div> <blockquote type="cite"> <div> On 15 December 2018 at 20:02 "C. Andrews Lavarre" < <a
2018 Dec 15
4
Upgrade to 2.3.1 has failed
Excellent, thank you again. The openssl command I have tried (that used to work with Dovecot 2.2) is: openssl s_client -connect mail.privustech.com:143 I have also tried ? ? ? ??openssl s_client -connect mail.privustech.com:143 -servername mail.privustech.com I've posted?the full output from this to?https://pastebin.com/eUSarQdx I've posted te full output?from?dovecot -n
2016 Jul 03
3
Postfix/dovecot: user unrecognized, file permissions being misread
Hello all. Have spent several days following the excellent tutorial: http://www.binarytides.com/install-postfix-dovecot-debian/ but still fail to have the user recognized and am getting log entries that the mail directories are 0755 when I can clearly see that they are 0774. Very puzzling, any help would be deeply appreciated. Best regards, Andy =========== Details =========== ? I can add
2018 Dec 15
2
Upgrade to 2.3.1 has failed
Alexander good afternoon. Thank you. I have spent the day learning about AppArmor: ? I've reviewed your link, found /etc/apparmor.d/ and its local/ directory. ? I ran aa-logprof?and it found the change in stat?to old-stat? that is discussed in the upgrade documentation. So I Allow (A)?that. There are no other reports. ? I followed the discussion on using yast to manage the profiles. I'm
2018 Dec 14
2
Upgrade to 2.3.1 has failed
Problem: We had Dovecot v2.2 working just fine under openSUSE Leap 42.3. But we upgraded openSUSE to Leap 15.0. In the process, Dovecot got upgraded from 2.2 to 2.3.1. It no longer works and I haven't figured out how to downgrade to the older working version. The key issue seems to be the change to requiring dh.pem and changing s sl_protocols to ssl_min_protocols.?I think I've navigated
2004 Oct 16
0
Re: winesetuptk0.72/tcltk-winesetuptk-0.72
> It's the configuration part that I was looking for some help with, but > as noted I can install neither winesetuptk nor wineinstall You don't need winesetuptk or wineinstall anymore, because wine automatically sets up a .wine directory with the appropriate contents. Also, the wine config file isn't needed to successfully run wine anymore. If you don't have a .wine
2018 Dec 14
0
Upgrade to 2.3.1 has failed
Am 14.12.2018 um 19:58 schrieb C. Andrews Lavarre: > Thanks for the input. I've checked out your suggestions (details below) > but unfortunately no joy. > I also restored my backup 10-ssl.conf. It indeed has the "<" sign with > a space before the explicit paths to the files: > ? ? ssl_cert = </etc/certbot/live/privustech.com/fullchain.pem > ? ? ssl_key =
2018 Dec 16
0
Upgrade to 2.3.1 has failed
permissions should be 644 or 444 owned by root. if the permissions are too open, ssl/dovecot will refuse to load them. you may even see a message about it if you have verbose messages/ check your sys logs. I had this problem once with certs that checked out fine, correct < in dovcot config but didn't load. chmod 644 /etc/ssl/certs/dovecot.cert /etc/ssl/private/dovecot.key fixed the
2018 Dec 16
3
Upgrade to 2.3.1 has failed
For what it's worth, this gives the server an A: https://www.ssllabs.com/ssltest/analyze.html?d=mail.privustech. com So there is no problem with the certificates and key... Thanks again. On Sun, 2018-12-16 at 09:19 -0500, C. Andrews Lavarre wrote: > So it's something else.? -------------- next part -------------- An HTML attachment was scrubbed... URL:
2016 May 05
3
Cannot connect to Dovecot IMAP or POP
Hello all. Thank you for your service. Easy when you know how, but presently I do not. After literally months of research and experimentation we simply cannot log into our PAM / apache2 / postfix / dovecot pop3/imap STARTTLS email server with an ordinary email client, e.g., Evolution or Thunderbird. We can connect to the host server in a host of different ways (no pun intended)?http, https, ssh,
2018 Dec 16
3
Upgrade to 2.3.1 has failed
Andy, This is just rude. You have been told multiple times that the less-than symbol is required to read the certificate from the file. Otherwise, the filename is parsed as if it is the certificate itself. Which yields garbage. If dovecot can't read that file, it is *not* dovecot's fault. You are simply not going to succeed until *you* figure out what security differences you have in
2018 Dec 15
0
Upgrade to 2.3.1 has failed
Am 15.12.2018 um 17:16 schrieb C. Andrews Lavarre: > to /etc/apparmor.d/local/usr.lib.dovecot.imap-login?but still > cannot login with either the mail client or with explicit openssl: it > complains > error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown > protocol:s23_clnt.c:794: Hi, that error above typically means to connect with SSL to STARTTLS or vice versa. Please
2018 Dec 16
0
Upgrade to 2.3.1 has failed
Phil hi. Thank you for explaining what the symbol does... so it is like the BASH?from symbol. OK.That is new information. So without it dovecot reads the path/to/file as if it were a hashed cert, which of course doesn't work. So with the symbol dovecot tries to follow the path to read the cert but for some reason cannot read it. Now, that is curious, since I can cat the path/to/file and read
2013 Feb 20
0
Help needed in setting up a simple ENC
puppet maser conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [master] classfile = $vardir/classes.txt localconfig = $vardir/localconfig user = root group = root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog =
2003 Nov 28
2
GLM FITTED VALUES TABLE
Hi all I have the following generalized linear problem. In a study of allergic responses, patients arriving at a clinic in Groote Schuur hospital were tested for sensitivity to a number of substances. Three of these were moulds: Cladosporium (C), Alternaria (F) and Aspergillius (T). Their level of sensitivity was measured on the Rast Scale as: 0: not allergic 1: mildly
2013 Jan 17
2
mcollective puppet plugin not working for centos
I have a test setup like this: host ======= *puppet-idc*: Ubuntu 12.04 running ActiveMQ, Mcollective, puppet agent and server *puppet-node1*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node2*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node3*: CentOS 6.3 running MCollective and puppet agent I installed the *mcollective-plugins-puppetd plugin* on all *3 Ubuntu
2023 Jan 11
1
problems with sysvol aft
Hi, I plan to upgrade/replace my somewhat crippled and outdated samba 4.7.4 domain controller. The OS is an openSUSE-Leap-42.3 which had no packages for a samba-ad-dc. These packages have been introduced in successor openSUSE releases starting with Leap-15.0. Leap-15.0 comes with samba 4.7.11. So I set up a new Leap-15.0 host and joint it as a dc controller. I set up the sysvol replication
2023 Jan 13
1
problems with sysvol after fsmo transfer
Hi Thorsten, hi Rowland, Am Donnerstag, 12. Januar 2023, 15:57:45 CET schrieb Thorsten Marquardt via samba: > Am 12.01.23 um 14:03 schrieb Rowland Penny via samba: > > On 12/01/2023 12:51, Rowland Penny via samba wrote: > >> On 12/01/2023 12:28, Thorsten Marquardt via samba wrote: > >>> srv-kb-dc1:~ # klist > >>> Ticket cache: DIR::/run/user/0/krb5cc/tkt