similar to: Dovecot 2.3-rc1 SMTP submission proxy always gives TLS required error even when already using TLS

On 2017-12-21 16:48, Stephan Bosch wrote: > Op 12/18/2017 om 9:44 PM schreef Michael Marley: > >> First of all, I apologize for my accidental empty message earlier. >> >> I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I >> try to connect to it, it always returns "530 5.7.0 TLS required." for >> any sort of AUTH or MAIL

On 2017-12-22 11:22, Michael Marley wrote: > On 2017-12-21 16:48, Stephan Bosch wrote: > > Op 12/18/2017 om 9:44 PM schreef Michael Marley: > > First of all, I apologize for my accidental empty message earlier. > > I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I > try to connect to it, it always returns "530 5.7.0 TLS required." for

Hi, I am running Dovecot 2.2.26.0 compiled against OpenSSL 1.1 and, since upgrading to OpenSSL 1.1.0c, the "lmtp" process has been crashing with SIGSEGV whenever it receives SIGINT. This always happens a minute or so after the lmtp process handles a message. It can also be manually reproduced by sending SIGINT to one of the running lmtp processes. I am compiling and running on an

Op 12/18/2017 om 9:44 PM schreef Michael Marley: > First of all, I apologize for my accidental empty message earlier. > > I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I > try to connect to it, it always returns "530 5.7.0 TLS required." for > any sort of AUTH or MAIL command.? This occurs even if TLS is being > used.? It also occurs regardless of

On 15.11.2016 13:27, Michael Marley wrote: > Hi, > > I am running Dovecot 2.2.26.0 compiled against OpenSSL 1.1 and, since > upgrading to OpenSSL 1.1.0c, the "lmtp" process has been crashing with > SIGSEGV whenever it receives SIGINT. This always happens a minute or so > after the lmtp process handles a message. It can also be manually > reproduced by sending

Hi You can't think how glad I am that SSL issues rise again in a new Dovecot version with next Ubuntu release with a new OpenSSL library. Some days ago I have posted something similar about Ubuntu 14.04 - Dovecot 2.2.9 - OpenSSL 1.0 (Dovecot processes turning zombie) but noone cared about. I still think is somehow related to ssl-param process + config + auth + ...whatever (all of them

?Reuben, could you try this: service auth-worker { ? executable = /usr/bin/strace -o /tmp/out /usr/libexec/dovecot/auth -w } and send the out file to me? I wasn't able to reproduce your problem with glibc-2.28. Aki On 31.08.2018 21:30, Aki Tuomi wrote: > Ah. Thanks for the pointer. > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From:

I think this might be caused by glibc 2.28. I saw a similar error with the "doveadm purge" command after upgrading my system to that version. Michael Marley On 2018-08-31 13:10, Aki Tuomi wrote: > I'll see if this is reproducible > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot at

It should work if you add it to apt. Directory listing is denied, which causes 403 if you access with browser. Aki -------- Original message --------From: Michael Marley <michael at michaelmarley.com> Date: 21/09/2018 18:00 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: v2.3.3 release candidate released On 2018-09-21 09:45, Timo Sirainen wrote: >

Hi i have the running i both sides, client and server sides the puppet 0.25.4 Get this error on server side: puppetmasterd[5363]: Report puppet_dashboard failed: wrong Content-Length format And receive this error on my client side: warning: Value of ''preferred_serialization_format'' (pson) is invalid for report, user default (b64_zlib_yaml) I am getting any reports on my

Hi, I am trying to do my first puppet configuration, already installed the puppetserver and client, in this link show my configuration and my puppet structure: http://paste.pocoo.org/show/212227/ But when i run the client side daemon i get this message: info: /Class[main]/Node[basenode]/Class[inittab]/File[inittab]/source: No specified sources exist err:

I am the system administrator. I have a system that was built with a default install which resulted in everything in a single file system except for /boot wrote some scripts to split out: /home, /usr, /var, /opt, and /tmp to separate file systems/logical volumes it looks like it ought to work, There's plenty of space in all the filesystems and I can log via ssh and have write access in my

Hello! Can I use DBM databases (as they are used in Perl) for the import of large datasets in R? Thanks in advance for your help, Petra Steiner - --------------------------------------------------- Petra Steiner Arbeitsbereich Linguistik Universitaet Muenster Huefferstrasse 27 48149 Muenster

hey guys, wanna know where to find my graphics card driver for centos5.5 coz the 5.4 support it and xserver start automaticly but the 5.5 doesnot start and tried to reconfigure the xorg.conf but it doesnot work too. and i noticed that the hardware prob process find a different driver for my card . mine is arrandle.intel! my system is a dell studio laptop 1569! thnx in advance -------------- next

This issue is peripherally related to the following thread Re: [Dovecot] client certs with godaddy ssl cert This is running on CentOS 5.2 with latest Atrpms for Dovecot as of this weekend. # rpm -qa | grep dovecot dovecot-sieve-1.1.5-8.el5 dovecot-1.1.4-0_81.el5 With assistance from Rainer Frey (Inxmail GmbH), I am able to successfully use client ssl certs for imap access on both my Nokia

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 26 Nov 2014, Mark Homoky wrote: > On 17/11/2014 07:23, Ron Leach wrote: >> On 16/11/2014 07:24, Robert Schetterer wrote (re-ordered): >>> Am 16.11.2014 um 02:24 schrieb Reindl Harald: >> >> Off topic for Dovecot list, but I might think instead about separate >> inbound and outbound MTAs to achieve

On 12/12/2017, 1:39:08 PM, Stephan Bosch <stephan at rename-it.nl> wrote: > However, keep in mind that for this particular feature we're just > providing the "chicken" as it were. The "egg", i.e. client support, is > still to come. Apart from Trojita (which I think is still not widely > used), I know of no IMAP client supporting BURL/URLAUTH for message

On 12/14/2017, 3:03:41 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > On 13.12.2017 21:41, Tanstaafl wrote: >> On 12/12/2017, 1:39:08 PM, Stephan Bosch <stephan at rename-it.nl> wrote: >> I thought this was simply going to be an SMTP like service that any SMTP >> client could utilize, keeping the BURL/URLAUTH pieces working only >> between Dovecot and the

Op 12/14/2017 om 6:07 PM schreef Tanstaafl: > One other point. > > Adding support for something like this that also requires Clients to add > support for it is just begging for a feature that never gets used. > > Stephan, are you sure there is no (fairly simple) way to make this an > SMTP service that any email client that supports SMTP can use? It already is a normal

On Sat Dec 16 2017 15:41:25 GMT-0500 (Eastern Standard Time), Tanstaafl <tanstaafl at libertytrek.org> wrote: > Ok, well, my ignorance is probably glaring here, but what I meant was, > the make the BURL/URLAUTH pieces strictly between Dovecot and the > backend SMTP server, make it invisible to the Client... So, I take it the no response to this means that there is no way to put the