Re: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS
And can you use the compiled spamdyke version from 11.3 on the new 12.1 machines ? Did you try to copy them to the new os? Then you can use TLS support for SMTP. -Ursprüngliche Nachricht- Von: spamdyke-users Im Auftrag von Pablo Murillo (rednet) via spamdyke-users Gesendet: Freitag, 23. Oktober 2020 00:21 An: Dirk Kannapinn via spamdyke-users Betreff: Re: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS I'm using now without TLS but I have to move around 50 servers from 11.3 to 12.1 !, anda I need to have TLS because allmost everyone are using smtp with tls, and going back to no-tls will be a big problem On 10/22/2020 5:33 PM, Dirk Kannapinn via spamdyke-users wrote: > Had the same issue after I moved from CentOS 6.10 to 8.2. > > I think it's related to the OpenSSL library 1.1.1. Tried it several > times but was unsuccessfully. It works if you compile it without SSL/TLS > support. > So I used the spamdyke I compiled on the old machine. It works on the > new one but is unable to use newer encryption techniques like TLSv1.3 > or modern ciphers. > > I wish Sam will create a new Spamdyke version which works with newer > Linux distributions. > > Dirk > > -Ursprüngliche Nachricht- > Von: Pablo Murillo (rednet) > Gesendet: Donnerstag, 22. Oktober 2020 22:11 > An: spamdyke users > Betreff: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS > > Hi > > I'm upgrading few server from FreeBSD 11.4 to 12.1 and I found that > the port fot SpamDyke is broken, so I compile "manually" and I found a > problem with OpenSSL Spamdyke is not finding openssl, and openssl is > installed > > ./configure --enable-tls --without-debug-output checking for gcc... gcc > checking whether the C compiler works... yes ... > checking if openssl/ssl.h will include without additional include > directories... yes checking for library containing RSA_sign... > -lcrypto checking for library containing SSL_library_init... no > configure: error: in `/root/spamdyke-5.0.1/spamdyke': > configure: error: --enable-tls was given but OpenSSL was not found > > I'm sending the config.log attached > > Pablo Murillo > > ___ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > https://spamdyke.org/mailman/listinfo/spamdyke-users ___ spamdyke-users mailing list spamdyke-users@spamdyke.org https://spamdyke.org/mailman/listinfo/spamdyke-users smime.p7s Description: S/MIME cryptographic signature ___ spamdyke-users mailing list spamdyke-users@spamdyke.org https://spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS
I'm using now without TLS but I have to move around 50 servers from 11.3 to 12.1 !, anda I need to have TLS because allmost everyone are using smtp with tls, and going back to no-tls will be a big problem On 10/22/2020 5:33 PM, Dirk Kannapinn via spamdyke-users wrote: Had the same issue after I moved from CentOS 6.10 to 8.2. I think it's related to the OpenSSL library 1.1.1. Tried it several times but was unsuccessfully. It works if you compile it without SSL/TLS support. So I used the spamdyke I compiled on the old machine. It works on the new one but is unable to use newer encryption techniques like TLSv1.3 or modern ciphers. I wish Sam will create a new Spamdyke version which works with newer Linux distributions. Dirk -Ursprüngliche Nachricht- Von: Pablo Murillo (rednet) Gesendet: Donnerstag, 22. Oktober 2020 22:11 An: spamdyke users Betreff: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS Hi I'm upgrading few server from FreeBSD 11.4 to 12.1 and I found that the port fot SpamDyke is broken, so I compile "manually" and I found a problem with OpenSSL Spamdyke is not finding openssl, and openssl is installed ./configure --enable-tls --without-debug-output checking for gcc... gcc checking whether the C compiler works... yes ... checking if openssl/ssl.h will include without additional include directories... yes checking for library containing RSA_sign... -lcrypto checking for library containing SSL_library_init... no configure: error: in `/root/spamdyke-5.0.1/spamdyke': configure: error: --enable-tls was given but OpenSSL was not found I'm sending the config.log attached Pablo Murillo ___ spamdyke-users mailing list spamdyke-users@spamdyke.org https://spamdyke.org/mailman/listinfo/spamdyke-users ___ spamdyke-users mailing list spamdyke-users@spamdyke.org https://spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS
Had the same issue after I moved from CentOS 6.10 to 8.2. I think it's related to the OpenSSL library 1.1.1. Tried it several times but was unsuccessfully. It works if you compile it without SSL/TLS support. So I used the spamdyke I compiled on the old machine. It works on the new one but is unable to use newer encryption techniques like TLSv1.3 or modern ciphers. I wish Sam will create a new Spamdyke version which works with newer Linux distributions. Dirk -Ursprüngliche Nachricht- Von: Pablo Murillo (rednet) Gesendet: Donnerstag, 22. Oktober 2020 22:11 An: spamdyke users Betreff: [spamdyke-users] FreeBSD 12.1 problems compiling with TLS Hi I'm upgrading few server from FreeBSD 11.4 to 12.1 and I found that the port fot SpamDyke is broken, so I compile "manually" and I found a problem with OpenSSL Spamdyke is not finding openssl, and openssl is installed ./configure --enable-tls --without-debug-output checking for gcc... gcc checking whether the C compiler works... yes ... checking if openssl/ssl.h will include without additional include directories... yes checking for library containing RSA_sign... -lcrypto checking for library containing SSL_library_init... no configure: error: in `/root/spamdyke-5.0.1/spamdyke': configure: error: --enable-tls was given but OpenSSL was not found I'm sending the config.log attached Pablo Murillo smime.p7s Description: S/MIME cryptographic signature ___ spamdyke-users mailing list spamdyke-users@spamdyke.org https://spamdyke.org/mailman/listinfo/spamdyke-users
[spamdyke-users] FreeBSD 12.1 problems compiling with TLS
Hi I'm upgrading few server from FreeBSD 11.4 to 12.1 and I found that the port fot SpamDyke is broken, so I compile "manually" and I found a problem with OpenSSL Spamdyke is not finding openssl, and openssl is installed ./configure --enable-tls --without-debug-output checking for gcc... gcc checking whether the C compiler works... yes ... checking if openssl/ssl.h will include without additional include directories... yes checking for library containing RSA_sign... -lcrypto checking for library containing SSL_library_init... no configure: error: in `/root/spamdyke-5.0.1/spamdyke': configure: error: --enable-tls was given but OpenSSL was not found I'm sending the config.log attached Pablo Murillo This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by spamdyke configure 5.0.1, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure --enable-tls --without-debug-output ## - ## ## Platform. ## ## - ## hostname = srv105.serversur.net uname -m = amd64 uname -r = 12.1-RELEASE-p10 uname -s = FreeBSD uname -v = FreeBSD 12.1-RELEASE-p10 GENERIC /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /home/rednet/bin ## --- ## ## Core tests. ## ## --- ## configure:2322: checking for gcc configure:2338: found /usr/local/bin/gcc configure:2349: result: gcc configure:2380: checking for C compiler version configure:2389: gcc --version >&5 gcc (FreeBSD Ports Collection) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:2400: $? = 0 configure:2389: gcc -v >&5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc9/gcc/x86_64-portbld-freebsd12.1/9.3.0/lto-wrapper Target: x86_64-portbld-freebsd12.1 Configured with: /var/ports/usr/ports/lang/gcc9/work/gcc-9.3.0/configure --enable-multilib --enable-plugin --with-build-config=bootstrap-debug --disable-nls --enable-gnu-indirect-function --libdir=/usr/local/lib/gcc9 --libexecdir=/usr/local/libexec/gcc9 --program-suffix=9 --with-as=/usr/local/bin/as --with-gmp=/usr/local --with-gxx-include-dir=/usr/local/lib/gcc9/include/c++/ --with-ld=/usr/local/bin/ld --with-pkgversion='FreeBSD Ports Collection' --with-system-zlib --enable-languages=c,c++,objc,fortran --prefix=/usr/local --localstatedir=/var --mandir=/usr/local/man --infodir=/usr/local/share/info/gcc9 --build=x86_64-portbld-freebsd12.1 Thread model: posix gcc version 9.3.0 (FreeBSD Ports Collection) configure:2400: $? = 0 configure:2389: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:2400: $? = 1 configure:2389: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files compilation terminated. configure:2400: $? = 1 configure:2420: checking whether the C compiler works configure:2442: gcc -Wall conftest.c >&5 configure:2446: $? = 0 configure:2494: result: yes configure:2497: checking for C compiler default output file name configure:2499: result: a.out configure:2505: checking for suffix of executables configure:2512: gcc -o conftest -Wall conftest.c >&5 configure:2516: $? = 0 configure:2538: result: configure:2560: checking whether we are cross compiling configure:2568: gcc -o conftest -Wall conftest.c >&5 configure:2572: $? = 0 configure:2579: ./conftest configure:2583: $? = 0 configure:2598: result: no configure:2603: checking for suffix of object files configure:2625: gcc -c -Wall conftest.c >&5 configure:2629: $? = 0 configure:2650: result: o configure:2654: checking whether we are using the GNU C compiler configure:2673: gcc -c -Wall conftest.c >&5 configure:2673: $? = 0 configure:2682: result: yes configure:2691: checking whether gcc accepts -g configure:2711: gcc -c -g conftest.c >&5 configure:2711: $? = 0 configure:2752: result: yes configure:2769: checking for gcc option to accept ISO C89 configure:2833: gcc -c -Wall conftest.c >&5 configure:2833: $? = 0 configure:2846: result: none needed configure:2873: checking how to run the C preprocessor configure:2904: gcc -E conftest.c configure:2904: $? = 0 configure:2918: gcc -E conftest.c conftest.c:9:10: fatal error: ac_nonexistent.h: No such file or directory 9 | #include | ^~ compilation terminated. configure:2918: $? = 1 configure: failed program was:
