Displaying 20 results from an estimated 1000 matches similar to: "Postfix/dovecot: user unrecognized, file permissions being misread"
2016 Jul 03
2
Postfix/dovecot: user unrecognized, file permissions being misread
On Sun, 2016-07-03 at 15:56 -0500, Edgar Pettijohn wrote:
> doveconf -n would be helpful
Thank you:
lavarre:/var/mail/vhosts/privustech.com # doveconf -n
# 2.2.18: /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.8 (0c4ae064f307+)
# OS: Linux 4.1.26-21-default x86_64 openSUSE 42.1 (x86_64) ext4
auth_mechanisms = plain login
auth_verbose = yes
listen = *
log_path = /var/log/dovecot.log
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
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
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 =
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,
2016 Jul 24
2
Dovecot cannot find mailboxes
Edgar, thank you for your help:
I have solved gaining access from a client (Evolution) via IMAP to the
server: I can refresh, add folders, and delete folders. But I am still
confounded, as IMAP does not see any mailboxes. Neither we from the
command line (telnet, openssl, login, select) nor the system can find
the mailbox, despite following FindMailLocation:
telnet, openssl, login, then
b
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 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 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:
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
2
Upgrade to 2.3.1 has failed
Am 15.12.2018 um 19:43 schrieb Aki Tuomi:
>> I've posted te full output from dovecot -n to https://pastebin.com/F8Ra
>> C4bt
You again broke your setup. From your pastebin:
ssl_cert = /etc/certbot/live/privustech.com/fullchain.pem
That's missing the "<" in front of the path to the certificate file.
Proably the same mistake for the ssl_key parameter.
Alexander
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
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 15
0
[Fwd: Re: Upgrade to 2.3.1 has failed]
Alexander hi.
Aki caught the STARTTLS issue as well, I corrected it, but it still
doesn't work.
Enjoy your weekend. I intend to enjoy mine!
:-)
Thanks again for your time.
Andy
-------- Forwarded Message --------
From: C. Andrews Lavarre <alavarre at gmail.com>
To: Aki Tuomi <aki.tuomi at open-xchange.com>
Subject: Re: Upgrade to 2.3.1 has failed
Date: Sat, 15 Dec 2018 15:08:58
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
2015 Sep 30
3
[IMAP] Nothing in INBOX
Hey all,
I've just installed Postfix + Dovecot on Xubunto 14.04 LTS.
Following this page :
Setup a mail server with Postfix and Dovecot on Ubuntu / Debian
<http://www.binarytides.com/install-postfix-dovecot-debian/>
although I'm able to send emails to GMail and other kind of domain, nothing
appears on Thunderbird INBOX, nor using openssl :
2018 Dec 15
0
Upgrade to 2.3.1 has failed
Alexander, Thanks, as described before, if I include the "<" then
Dovecot fails to start at all.
Thank you again for your time. I have forwarded my latest to Aki to the
group.
Enjoy your weekend.
Best regards, Andy
On Sat, 2018-12-15 at 23:08 +0100, Alexander Dalloz wrote:
> Am 15.12.2018 um 19:43 schrieb Aki Tuomi:
> >
> > >
> > > I've posted te full
2007 Dec 29
2
DO NOT REPLY [Bug 5166] New: -o -g options don't work right or I've misread the man pages
https://bugzilla.samba.org/show_bug.cgi?id=5166
Summary: -o -g options don't work right or I've misread the man
pages
Product: rsync
Version: 2.6.6
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2015 Oct 01
0
[IMAP] Nothing in INBOX
Hello Yvon,
On 30.09.2015 15:14, Yvon Thoraval wrote:
> I've just installed Postfix + Dovecot on Xubunto 14.04 LTS.
> Following this page :
> Setup a mail server with Postfix and Dovecot on Ubuntu / Debian
> <http://www.binarytides.com/install-postfix-dovecot-debian/>
>
> although I'm able to send emails to GMail and other kind of domain, nothing
> appears on