Re: a bit further along - OpenSSL - Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread Joseph Tam
Jerry Kemp wrote: same ENV variable setup and configure statement as originally used, but again, :( ended up failing here: .. libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes

Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread Jerry Kemp
On 08/25/17 04:08 PM, Joseph Tam wrote: # ./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

Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread Jerry Kemp
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

a bit further along - back to Dovecot compile - Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread Jerry Kemp
After I confirmed I had everything correct with OpenSSL (including successful 'make test'), went back to try a recompile of Dovecot. same ENV variable setup and configure statement as originally used, but again, :( ended up failing here:

a bit further along - OpenSSL - Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread Jerry Kemp
a bit further along, but not quite there yet! Hello James, thanks for kicking me off in the right direction. Couple of additional details, using GCC for a compiler. And, at least for now I am going to focus on the 32 bit compile. I do not ever see dovecot handling Gb sized files on this

Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread Joseph Tam
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

Install still locks up my server

2017-08-25 Thread Marc Perkel
This is still broken in the 2.2.32. config.guess forks copies till the server dies. Running Centos 6.6 under OpenVZ. On 06/26/17 16:03, Marc Perkel wrote: On 06/26/17 14:42, Timo Sirainen wrote: On 26 Jun 2017, at 23.19, Marc Perkel wrote: Ever since 2.26 I haven't been

Re: dovecot: config: Error: BUG: Config client connection sent too much data

2017-08-25 Thread Tony
Hello, Absolutely. Here is the output of doveconf -n: # doveconf -n # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.9.36-x86_64-linodexx x86_64 Arch Linux auth_mechanisms = plain login base_dir = /var/run/dovecot/ dict { expire =

Re: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

2017-08-25 Thread James
On 25/08/2017 04:52, Jerry Kemp wrote: Hello Jerry, attempting to compile dovecot 2.2.31 on Sun/Oracle Solaris 10 SPARC. It worked for me so you should make it to your goal. configure goes fine. First sign of problems during compile is with this warning:

Re: Dovecot - Postfix Calender Synchronisation

2017-08-25 Thread Rupert Gallagher
> handle big number of users and big amount of data. You must be working for the NSA. Sent from ProtonMail Mobile On Fri, Aug 25, 2017 at 2:15 PM, Robert Wolf wrote: > On Thu, 24 Aug 2017, Rupert Gallagher wrote: > Re: dependencies > > - db: > why? just use the ical

Re: Dovecot - Postfix Calender Synchronisation

2017-08-25 Thread Robert Wolf
On Thu, 24 Aug 2017, Rupert Gallagher wrote: > Re: dependencies > > - db: why? just use the ical and vcard files! They are files, they are in a > directory, they can be used like dovecot uses eml files! No need for > postgresql or mysql. *** Usually, the DB server is one host, Webclient

Re: dovecot: config: Error: BUG: Config client connection sent too much data

2017-08-25 Thread Aki Tuomi
On August 25, 2017 at 9:11 AM Tony wrote: Hello, Today I started noticing a very odd Dovecot error in the mail logs across 2 replicated Dovecot hosts via dsync. I have searched the Dovecot archives, Google, back tracked, downgraded Dovecot to earlier versions from

Re: Dovecot - Postfix Calender Synchronisation

2017-08-25 Thread Robert Schetterer
Am 23.08.2017 um 10:09 schrieb Maurizio Caloro: > Hello Together > > > > Please witch add-on possibilities exist to synchronize the Calednar with > Dovecot and Postfix. > > Can give me here any a possible direction ? > > > > thanks regards > > Mauri > > > This has mostly ( there is

Re: socketpair failed: Too many open files on Debian 9

2017-08-25 Thread Patrick Westenberg
Hi, I think LimitNOFILE=infinity solved my problem. No errors since almost two days. Thanks! Patrick Hajo Locke schrieb: > Hello, > > are you using systemd? May be you have to edit unit-file for > dovecotservice and increase filelimit > > LimitNOFILE=infinity > > Hajo > > Am 23.08.2017

Re: Dovecot - Postfix Calender Synchronisation

2017-08-25 Thread Roger Klorese
On Thu, Aug 24, 2017 at 11:28 PM Rupert Gallagher wrote: > On Thu, Aug 24, 2017 at 10:55 PM, Roger Klorese > wrote: > > > "Webmail? We use dovecot." And how exactly do you read and write mail > using dovecot? > > With a MUA. > And you’re suggesting

Re: Dovecot - Postfix Calender Synchronisation

2017-08-25 Thread Rupert Gallagher
On Thu, Aug 24, 2017 at 10:55 PM, Roger Klorese wrote: > "Webmail? We use dovecot." And how exactly do you read and write mail using > dovecot? With a MUA.

dovecot: config: Error: BUG: Config client connection sent too much data

2017-08-25 Thread Tony
Hello, Today I started noticing a very odd Dovecot error in the mail logs across 2 replicated Dovecot hosts via dsync. I have searched the Dovecot archives, Google, back tracked, downgraded Dovecot to earlier versions from earlier this year and ruled everything out I could think of to no avail.