Hello Joseph,

Thanks for the reply. Please see inline comments:

On 08/25/17 04:08 PM, Joseph Tam wrote:

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.

James (from the 1st reply) comments that this is a common output and is of no concern. Wondering if someone else can validate?

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 need it).

I did this stuff specifically because the system has some old OpenSSL 0.9.7* stuff that is obviously obsolete and insecure, but cannot be removed. In short, I did not want for the Dovecot configure script to find or try to use any of that stuff.

Maybe check output of

file /Applications/openssl-1.0.2l.32/lib/libssl.so.1.0.0

# file /Applications/openssl-1.0.2l.32/lib/libssl.so.1.0.0

/Applications/openssl-1.0.2l.32/lib/libssl.so.1.0.0: ELF 32-bit MSB dynamic lib SPARC Version 1, dynamically linked, not stripped, no debugging information available

# ls -l /Applications/openssl-1.0.2l.32/lib/libssl.so.1.0.0

-r-xr-xr-x 1 root root 424708 Aug 25 16:17 /Applications/openssl-1.0.2l.32/lib/libssl.so.1.0.0

#

just to make sure your library's arhitecture matches your expectation.

...

# ./configure
--prefix=/Applications/dovecot-2.2.31.32
--with-ssl=openssl
--with-ssldir=/Applications/dovecot-2.2.31.32/certs
--with-storages=mbox,maildir,imapc,pop3c

I believe "--with-storages" option is now obsolete: all the storage backends are built, whether you ask for it or not.

Joseph Tam <jtam.home@gmail.com>