Displaying 20 results from an estimated 100 matches similar to: "Dovecot cannot find mailboxes"
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 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
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 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 =
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 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 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
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 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 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
2016 Oct 15
2
First steps in Dovecot; IMAP not working
Le 15 oct. 2016 ? 9:56, mick crane <mick.crane at gmail.com> a ?crit:
> I assume this means there are no emails in the INBOX.
> send yourself a mail.
This is actually one of the first thing I tried when I saw outgoing mails worked. I also tried sending mails from another address, hoping to receive an error message back, but nothing got received.
I now think the INBOX itself doesn?t
2014 Sep 17
1
unable to see mail when using telnet / open ssl
Dear dovecot list.
I'm setting up my own VPS and working through getting mail to work.
Here is my dovecot -n
$dovecot -n
maildir:%h/%d/%n/mail : layout=fs
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login cram-md5
auth_verbose = yes
auth_verbose_passwords = plain
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
2014 Apr 23
0
Something went wrong
http://secret-brushlands-1375.herokuapp.com/users/sign_up
Not sure why all of a sudden I am getting this error message when I try
to save a new user -
Here is the log file:
C:\rails_projects\store4>heroku logs
2014-04-23T21:35:54.918695+00:00 app[web.1]:
vendor/bundle/ruby/2.0.0/gems/act
ivesupport-4.1.0/lib/active_support/callbacks.rb:113:in `call'
2014-04-23T21:35:54.918698+00:00
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
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