similar to: Error starting 1.0.15 with SSL_DISABLE=No

On 2015-06-10 12:22:45 -0400, Steve Matzura wrote: > When starting Dovecot 1.0.15 after building it from source using the > standard procedure, I receive the following message when starting, > even though SLL_DISABLE=No: > > Error: SSL support not compiled in but ssl_disable=no > Fatal: Invalid configuration in /usr/local/etc/dovecot.conf > > How is SSL support configured

On advice/recommendation received on this list, I removed version 1.0.15 with: rm -rf /usr/local/dovecot However, now that I have version 2 properly installed, configured, and ready to start testing with Postfix, it appears the old version is still in /usr/local/sbin, /usr/local/include, /usr/local/libexec, /usr/local/lib and /usr/local/shared/doc. Thinking that anything in /usr/local is

I mean, in the source directory. On 12 June 2015 at 15:13, Muzaffer Tolga Ozses <tolga at ozses.net> wrote: > Have you done *make distclean* in prior? That should remove all things > dovecot. > > On 12 June 2015 at 15:10, Steve Matzura <number6 at noisynotes.com> wrote: > >> On advice/recommendation received on this list, I removed version >> 1.0.15 with:

Peter, Any objections to adding this to the trunk? When I run 'ldd upsc' without this patch, it lists the OpenSSL libraries, and the default ./configure setting is to not use OpenSSL. - Charles > Log: > If we are not using SSL_CFLAGS or SSL_LDFLAGS, do not add the OpenSSL libraries > to all of the binaries. > > > Modified: branches/deb_fixes_for_trunk/configure.in >

Hi, I have a problem after upgrading dovecot 1.0rc1 to 1.0rc6. I don't use SSL at all so I have 'ssl_disable = yes' in my configuration. This works fine in 1.0rc1 but dovecot 1.0rc6 failed to start with the following error message "dovecot: Login process died too early - shutting down". Setting 'ssl_disable = no' resolves the problem but now dovecot announce TLS

After applying some changes to 10-master.conf as detailed at http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I receive the following when trying to start: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf line 49: Expecting '{' I'm trying to enable LMTP. The instructions say: Socket configuration The actual socket is configured in

My /var/log/maillog was getting pretty big because of lots of testing and re-configuring I've been doing lately with both Dovecot and Postfix. I figured just remove /var/log/maillog and it would be re-created. It wasn't--not by Dovecot, not by Postfix. I had to manually create a new one, put one character in it, save it, properly secure it with chmod, and then Dovecot (and postfix)

Hello Dovecot users! There seems to be a new dependency in some modules (eg, lib-storage, libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those modules didn't require OpenSSL, but 2.1 does. For the linking process the path to the OpenSSL library isn't specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL is in a non-standard path. (Haven't checked if SSL_CFLAGS

Tags: patch, upstream Hi, when configuring nut 2.2.0 the variable/symbol `@SSL_LDFLAGS@' is not resolved by the libupsclient-config script. The attached patch changes `@SSL_CFLAGS@' to `@LIBSSL_CFLAGS@' `@SSL_LDFLAGS@' to `@LIBSSL_LDFLAGS@' which should solve this issue. Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/

Hi, I am running into a interesting issue with Dovecot. I compiled Dovecot 2.0.7 with LD_RUN_PATH set to /xsys/lib and it was able to find and link against the correct OpenSSL libraries (/xsys/lib), the generated Makefile look OK. Here is a snippet of the SSL cflags and libs. SSL_CFLAGS = -I/xsys/include SSL_LIBS = -L/xsys/lib -lssl -lcrypto -ldl After I compil, install and run Dovecot I

Sorry for having lost the original chain of this problem. It's been a very long day. New output from 'dovecot -n output', including the contents of dovecot.conf, conf.d/10-master.conf, conf.d/10-mail.conf and conf.d/10-ssl.conf: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS ext4

On Thu, 21 May 2015 19:21:41 -0500, you wrote: > >On May 21, 2015, at 9:25 AM, Steve Matzura wrote: > >> I needed to receive a message to admin at mydomain.com. I waited and >> waited for it, but it never showed up in the admin mailbox on the >> mydomain.com machine. So I looked for the admin account in >> /etc/dovecot.passwd, and there it was, plain-text password

Am Freitag, den 12.06.2015, 09:15 -0400 schrieb Steve Matzura: > On Fri, 12 Jun 2015 15:14:03 +0300, you wrote: > > > I mean, in the source directory. > > You mean in the directory where files from the tar were placed? I've > unfortunately removed those manually, but then I put them back and > tried the make again, still same error. "make: *** No rule to make

Have you done *make distclean* in prior? That should remove all things dovecot. On 12 June 2015 at 15:10, Steve Matzura <number6 at noisynotes.com> wrote: > On advice/recommendation received on this list, I removed version > 1.0.15 with: > > rm -rf /usr/local/dovecot > > However, now that I have version 2 properly installed, configured, and > ready to start testing

On Fri, 12 Jun 2015 15:14:03 +0300, you wrote: >I mean, in the source directory. You mean in the directory where files from the tar were placed? I've unfortunately removed those manually, but then I put them back and tried the make again, still same error. "make: *** No rule to make target `distclean'. Stop. >On 12 June 2015 at 15:13, Muzaffer Tolga Ozses <tolga at

*make clean* then? On 12 June 2015 at 15:52, Steve Matzura <number6 at noisynotes.com> wrote: > On Fri, 12 Jun 2015 15:13:18 +0300, you wrote: > > >Have you done *make distclean* in prior? That should remove all things > >dovecot. > > I tried, but got: > > make: *** No target to make `distclean'. Stop. >

On Tue, 16 Jun 2015 22:02:29 +0200, you wrote: >Am Dienstag, den 16.06.2015, 11:44 -0400 schrieb Steve Matzura: >> The next phase of my testing procedure involves the simple act of >> delivering mail to my test box. When I send a message to either a >> valid or relayed user at my remote machine's address, it never gets >> there. I know this virtually for sure

Since I've decided to go to version 2, which is a lot more difficult to set up because I have to look in a lot more places than I did with version 1.0.15, what do I do with the old dovecot/passwd or its contents? I see no references to it in any of the stuff in conf.d or doc/dovecot/wiki. As always, thanks in advance.

I would also check where the "... is not portable!" messaage is generated. If it's done by the configure script, you can look at the test to give you a hint as to why this message was generated. For my setup, I did much the same as you but didn't have to set the SSL_CFLAGS, SSL_LIBS environment variables, nor did I set the --with-ssldir configure option (although your setup may

Look at /etc/hosts ::1 is the ipv6 version of localhost.? Sent from Samsung tablet -------- Original message -------- From Steve Matzura <number6 at noisynotes.com> Date: 06/13/2015 6:00 AM (GMT-06:00) To dovecot <dovecot at dovecot.org> Subject Testin new installation The first place I went to for test advice and planning recommendations was