similar to: Dovecot 2.0.rc3 doesn't compile with custom OpenSSL

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

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

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

Hi anyone. When I run make trying to compile Dovecot for a network attached storage box and it fails. I have used two variants of configuration: The first ./configure i_cv_epoll_works=no i_cv_inotify_works=no i_cv_posix_fallocate_works=no i_cv_signed_size_t=no i_cv_gmtime_max_time_t=32 i_cv_signed_time_t=yes i_cv_mmap_plays_with_write=yes i_cv_fd_passing=yes i_cv_c99_vsnprintf=yes

Dear Dovecot developers! This problem already existed some years ago, has been fixed, and now it's there again in Dovecot 2.2.25 (2.2.24 was fine). I'm running CentOS 6 with a custom OpenSSL installation in /usr/local/ssl Therefore, Dovecot is configured like this: env SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -lcrypto

I'm done. Good to go. Good compile + new binaries all built against the latest OpenSSL libraries. Big thank you to James, Joseph Tam and Aki Tuomi who game me pointers and kept me in the right direction. ........................................................................ These are the settings that made everything work for me. First, needed a current, up-to-date version of OpenSSL

Hello, I'm looking into adding support for extracting the username from client certificate's rfc822Name (from the subjectAltName extension). The question I have is what would be the best approach to do this? Current implementation has a kind of clean code since it just goes through the subject name, extracting the values with X509_NAME_get_text_by_NID (while NID is obtained with

I'm having an issue with Thunderbird (and Opera) and Dovecot SSL on a Solaris 10. My OS is Solaris 10 6/06 x86 (running in 64-bit mode) using ZFS (disk mirror) as the filesystem for my users. Dovecot version is 1.0rc7 (logs below are from 1.0rc6). First the connection asks if the SSL-certificate should be accepted, accepting it seems to work but then nothing happens. Thunderbird is

Hello, I tried to compile Dovecot 2.2.5 on Debian 6 with an alternate OpenSSL installation located at /usr/local/ssl A compilation with CPPFLAGS="-I/usr/local/ssl/include" \ LDFLAGS="-L/usr/local/ssl/lib -Wl,-rpath=/usr/local/ssl/lib" \ SSL_LIBS="-L/usr/local/ssl/lib -Wl,-rpath=/usr/local/ssl/lib" \ ./configure \ --prefix=/opt/dovecot-2.2.5 \ --enable-asserts \

attempting to compile dovecot 2.2.31 on Sun/Oracle Solaris 10 SPARC. configure goes fine. First sign of problems during compile is with this warning: ............................................... *** libssl_iostream_openssl.so is not portable! ............................................... actual ERRORS - Soon, compile errors out with undefined symbols. Output at bottom of note.

Hello. I hope someone out there can help with this. It is getting pretty urgent. I am running a Solaris 10 server on Opteron (amd64) hardware and have compiled Dovecot 1.0beta8 from source. It has openssl compiled in (after much mucking around with various environment variables and modifying the Makefile), and was built with: $ ./configure --with-ldap --with-ssl-dir=/etc/ssl $ make # make

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 list, I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 rpmbuild --define 'rhel 64' -ba dovecot-2.2.spec I get this error: checking for C compiler default output file name... configure: error: in `/home/builder/rpmbuild/BUILD/dovecot-2.2.2': configure: error: C compiler cannot create executables See `config.log' for more details. (config.log

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/

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 and built in? I know it has something to do with the --SSL_CFLAGS flag.

Thanks Buddy, I got it working. It was giving error when running make 'undefined reference to `request_init' etc' then I ran it with gmake LDFLAGS+=-lwrap and it worked and everything is working fine. Thanks again for your help Thankyou Tahir Riaz Assistant Director (Systems) COMSATS Internet Services COMSATS Headquarters Building 9, Shahrah-e-Jamhuriat, G-5/2 Islamabad.

Dear Stanislav, thanks for your patch. The problem with your "recommended" pkgconfigdir is that in many cases, it does not work. Namely, when ${prefix} is not one of the standard places such as /usr. As I understand it, the whole point of a tool like pkgconfig is to allow other software to automatically detect the install location of NUT, especially when that location is not one of

Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> ldd /usr/local/Dovecot-2.2.25/lib/dovecot/libssl_iostream_openssl.so >> linux-gate.so.1 => (0x00e8c000) >> libcrypto.so.1.0.0 => not found >> libssl.so.1.0.0 => not found >> librt.so.1 => /lib/librt.so.1 (0x00be4000) >> libc.so.6 => /lib/libc.so.6

hi all, a few notes/issues re: building dovecot on OSX. first, after DL of cvs-head, % autogen.sh reports: autogen.sh: line 2: libtoolize: command not found o OSX, 'libtoolize' has been sed'd to glibtoolize. couple of ways to deal with this: (a) edit in autogen.sh aclocal --- libtoolize --force +++ glibtoolize --force automake --add-missing autoheader autoconf (b)

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