Displaying 20 results from an estimated 2000 matches similar to: "Cannot connect to Dovecot IMAP or POP"
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
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 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
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 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
2007 Oct 12
1
use ps -ef check service have some error.
hi,all.
I found that use the ps -ef command to check a service status
have some error. I test it .
run puppetd --debug --tags apache2 ,get this message.
=============
debug: Service[apache2](provider=debian): Executing ''ps -ef''
debug: Service[apache2](provider=debian): PID is 12062
============
but the apache2 service is not running. and if I run ps -ef|grep
apache2
2010 Aug 20
5
puppet dashboard gui looks odd from apache2
I downloaded the puppet-dashboard.git from
http://github.com/puppetlabs/puppet-dashboard and did the installation
in my
ubuntu lucid puppet server following the steps in "Installation".
Now I can run it fine using the WEBrick like this
root@sys-ubuntu { ~/git/puppet-dashboard }$ ./script/server -e production
=> Booting WEBrick
=> Rails 2.3.5 application starting on
2010 Mar 04
3
Dependency cycles, please help.
Hi,
I''m having trouble writing a recipe to handle apache/passenger.
First, here is my apache2 class, found here :
http://www.reductivelabs.com/trac/puppet/wiki/Recipes/DebianApache2Recipe
---------------------------------------------
$apache2_sites = "/etc/apache2/sites"
$apache2_mods = "/etc/apache2/mods"
class apache2 {
[...]
define module ( $ensure =
2015 Apr 13
2
How to discern when like dir names exist in 2 places
with these rsync rsync [...] /var/ /dir/
rsync [...] /etc/ /dir2/
And exclude file: excl
/apache2/*
That will exclude both /var/apache2/*
and /etc/apache2/*
How can I tell rsync I want /var/apache2 excluded, but not /etc/apache2?
I mean short of using separate excl files for each run
Using something like the start of an absolute name:
2014 Jun 10
1
apache server-status permission denied
Hey all,
I'm having a slightly weird issue with apache server-status on just one of
my nodes.
In my httpd.conf I have the following:
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from 127.0.0.1 10.10.160
</Location>
If I do a ps grep I know that I'm using the right config:
[root at webhosta apache2]# ps -ef |
2013 Jan 31
1
The way Puppet installs things fail
Basically, the way puppet installs things things with
/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install
<package_name>
fails due to authentication
WARNING: The following packages cannot be authenticated
But if I do it from an ssh console normally, using apt-get install
<package_name> it works fine without issues.
Is there a way to change how puppet uses the