search for: privustech

...------------------------------------ Log Entries --------------------- --------------- # tail /var/log/mail postfix/qmgr[16390]: 9D6E8C1A77: from=<alavarre at gmail.com>, size=2794, nrcpt=1 (queue active) Message has been received postfix/lmtp[16770]: C218DC197D: to=<alavarre at privustech.com>, relay=mail.privustech.com[private/lmtp], delay=2560, delays=2260/0.01/300/0, dsn=4.4.2, status=deferred (conversation with mail.privustech.com[private/lmtp] timed out while receiving the initial server greeting) lmtp is not working ------------------------------------ # tail /var/l...

...uration testing details ======================= System is: Linux openSUSE Leap 42.1 Dovecot --version 2.2.18, Postfix Version: 2.11.6-3.1 Apache2 Version: 2.4.16-9.1 Connections 1. Evolution or Thunderbird to pop3 or imap reports: The reported error was "Could not connect to mail.privustech.com: Connection refused". Both connect successfully to googlemail.com with the same protocol: Port 993 SSL on a dedicated port I have also tried Port 143 STARTTLS after connecting without success 2. openssl s_client -connect mail.privustech.com:xxx a. xxx=25, 11...

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 to?https://pastebin.com/F8Ra C4bt Thank you again, Andy On...

...enssl, login, select) nor the system can find the mailbox, despite following FindMailLocation: telnet, openssl, login, then b select inbox * 0 EXISTS * 0 RECENT and postfix fails with 2016-07-23T21:22:37.312039-04:00 lavarre postfix/error[17088]: A8DA2C1BB2: to=<andy at privustech.com>, orig_to=<andy>, relay But the mailboxes do exist in /var/mail/vhosts/privustech.com/andy and we point to them in /etc/dovecot/users. doveconf -n is attached. ----- Two issues are: 1. file permissions and ownership 2. virtual versus system users 1. It appears that having the corr...

...id PEM certificate. We have followed the instructions at? https://wiki.dovecot.org/S SL/DovecotConfiguration 1. We have created /etc/dovecot/dh.pem (yes it took five hours)? 2. We have edited 10-ssl.conf as directed by the Wiki: ssl = yes ssl_cert = /etc/certbot/live/privustech.com/fullchain.pem ssl_key = /etc/certbot/live/privustech.com/privkey.pem ssl_dh = /etc/dovecot/dh.pem #(yes, it took five hours to create...) ssl_min_protocol = TLSv1 ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES...

...g 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 = </etc/certbot/live/privustech.com/fullchain.pem ? ? ssl_key = </etc/certbot/live/privustech.com/privkey.pem ?It returns several complaints after restarting dovecot which I addressed: ? ??https://wiki2.dovecot.org/Upgrading/2.3 ? ??https://github.com/dovecot/core/blob/master/doc/example-config/conf .d/10-ssl.conf ? Changed ss...

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 mail_debug = yes mail_location = mail...

...GUI yast, only the ncurses version and it does not contain editing, only adding, profiles. I tried creating a profile for imap-login?with that method and scanned for any issues, there were none reported, but still cannot log in. ? I followed the local/README to explicitly add /etc/certbot/live/privustech.com/* r, 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: I check yast2 sw_single for the dovecot insta...

...e instructions at? https://wiki.dovecot.org/S > SL/DovecotConfiguration > 1. We have created /etc/dovecot/dh.pem (yes it took five > hours)? > > 2. We have edited 10-ssl.conf as directed by the Wiki: > ssl = yes > ssl_cert = > /etc/certbot/live/privustech.com/fullchain.pem > ssl_key = /etc/certbot/live/privustech.com/privkey.pem > ssl_dh = /etc/dovecot /dh.pem #(yes, it took five hours to create...) Hi! You should use ssl_cert =</etc/certbot/live/privustech.com/fullchain.pem ssl_key =</etc/certbot/liv...

...<div> <br> </div> <div> Excellent, thank you again. </div> <div> The openssl command I have tried (that used to work with Dovecot 2.2) </div> <div> is: </div> <div> openssl s_client -connect mail.privustech.com:143 </div> <div> I have also tried </div> <div> openssl s_client -connect mail.privustech.com:143 -servername </div> <div> mail.privustech.com </div> <div> I've posted the full output from this t...

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: <https://dovecot.org/pipermail/dovecot/attachm...

...e: > 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 = </etc/certbot/live/privustech.com/privkey.pem Hi, the syntax you see in the documentation is mandatory. Your issue is really a permissions problem. Check your AppArmor setup. The path you use for storing the chained certificate and the private key is ce...

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

...rote: > Am 15.12.2018 um 19:43 schrieb Aki Tuomi: > > > > > > > > I've posted te full output from dovecot -n to https://pastebin.co > > > m/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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot...

...in dovcot config but didn't load. chmod 644 /etc/ssl/certs/dovecot.cert /etc/ssl/private/dovecot.key fixed the problem regards, Tim On 16/12/2018 14:33, C. Andrews Lavarre wrote: > 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: <https://dov...

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