slow mailbox refreshes

2018-07-09 Thread Fabian A. Santiago
Hello, I am using dovecot 2.3.2 on my private email server in conjunction with: centos 7.5 apache 2.4.6 mariadb 10.2.16 roundcube mail 1.3.6 php 5.6.36 postfix 2.10.1 I have one mailbox with nearly 30k messages in it dispersed across several folders. it's often very slow in refreshing the

Re: question about using cram-md5 login passwords

2018-04-23 Thread Fabian A. Santiago
On April 23, 2018 9:45:22 AM EDT, Aki Tuomi <aki.tu...@dovecot.fi> wrote: > >> On 23 April 2018 at 16:14 "Fabian A. Santiago" ><fsanti...@garbage-juice.com> wrote: >> >> >> hello dovecot community, >> >> question; if my user da

question about using cram-md5 login passwords

2018-04-23 Thread Fabian A. Santiago
hello dovecot community, question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login method again in the future,

Re: 2.3.1 from ghettoforge-testing causes auth failures

2018-03-29 Thread Fabian A. Santiago
On March 28, 2018 8:23:42 PM EDT, "Fabian A. Santiago" <fsanti...@garbage-juice.com> wrote: >Hello, > >I updated today to v2.3.1 from @gf-testing and it broke my imap auth >mechanism. My dovecot-imap.log reported: > >Temporary auth service failure >

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-29 Thread Fabian A. Santiago
On December 29, 2017 9:50:37 AM EST, Alexander Dalloz <ad+li...@uni-x.org> wrote: >Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago: >> December 28, 2017 6:38 PM, "Peter" <pe...@pajamian.dhs.org> wrote: >> >>> On 29/12/17 10:00, Fabian A. Santiago w

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-29 Thread Fabian A. Santiago
December 28, 2017 6:38 PM, "Peter" <pe...@pajamian.dhs.org> wrote: > On 29/12/17 10:00, Fabian A. Santiago wrote: > >> i've now completely uninstalled all traces of dovecot and reinstalled >> from your repo and still the same issue persists with the same >>

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-28 Thread Fabian A. Santiago
December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsanti...@garbage-juice.com> wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tu...@dovecot.fi> wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" >>> <fs

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-28 Thread Fabian A. Santiago
December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tu...@dovecot.fi> wrote: >> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" >> <fsanti...@garbage-juice.com> wrote: >> >> December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tu

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-28 Thread Fabian A. Santiago
December 28, 2017 12:43 PM, "Fabian A. Santiago" <fsanti...@garbage-juice.com> wrote: > December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tu...@dovecot.fi> wrote: > >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >>> &

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-28 Thread Fabian A. Santiago
December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tu...@dovecot.fi> wrote: >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >> <fsanti...@garbage-juice.com> wrote: >> >> Hello, >> >> After upgrading to dovecot 2

dovecot-pigeonhole problems after upgrade to v2.3.0

2017-12-28 Thread Fabian A. Santiago
Hello, After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports: Dec 28 12:05:07 mail

Re: 2.3.0 upgrade from 2.2.x

2017-12-27 Thread Fabian A. Santiago
On December 27, 2017 8:07:18 PM EST, "Fabian A. Santiago" <fsanti...@garbage-juice.com> wrote: >Question; So after updating to 2.3.0 and following the recommended >warnings / changes from running doveconf -n and then doing that same >command > "a new conf file&q

2.3.0 upgrade from 2.2.x

2017-12-27 Thread Fabian A. Santiago
Question; So after updating to 2.3.0 and following the recommended warnings / changes from running doveconf -n and then doing that same command > "a new conf file", and then renaming the conf files and restarting dovecot, I should be good to go with my old config updated to the new config spec?

Re: Package repository now available

2017-12-27 Thread Fabian A. Santiago
On December 27, 2017 4:38:02 PM EST, Aki Tuomi <aki.tu...@dovecot.fi> wrote: > >> On December 27, 2017 at 6:11 PM Aki Tuomi <aki.tu...@dovecot.fi> >wrote: >> >> >> >> > On December 27, 2017 at 6:05 PM "Fabian A. Santiago" ><fsa

Re: Package repository now available

2017-12-27 Thread Fabian A. Santiago
December 27, 2017 11:06 AM, "Fabian A. Santiago" <fsanti...@garbage-juice.com> wrote: > December 27, 2017 10:53 AM, aki.tu...@dovecot.fi wrote: > >> Small amendment... >> >> if you ran >> >> gpg --export > /etc/apt/trusted.gpg.d/dov

Re: Package repository now available

2017-12-27 Thread Fabian A. Santiago
December 27, 2017 10:53 AM, aki.tu...@dovecot.fi wrote: > Small amendment... > > if you ran > > gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg > > please run > > gpg --export ED409DA1 > /etc/apt/trusted.gpg.d/dovecot.gpg > > Aki > >> On December 27, 2017 at 5:00 PM aki.tu...@dovecot.fi

Re: hosting emails at home

2017-12-10 Thread Fabian A. Santiago
On December 10, 2017 5:25:46 PM EST, Stephan H <her...@gmail.com> wrote: >Which part? Hosting the email server at home or the relay in the >cloud? > >On Dec 10, 2017 14:53, "Fabian A. Santiago" ><fsanti...@garbage-juice.com> >wrote: > >> On

Re: hosting emails at home

2017-12-10 Thread Fabian A. Santiago
>On Dec 10, 2017 2:37 PM, "Fabian A. Santiago" ><fsanti...@garbage-juice.com> >wrote: > >> On December 10, 2017 2:49:35 PM EST, "André Rodier" <an...@rodier.me> >> wrote: >> >Hello Mike, >> > >> >Yes, I am using a static I

Re: hosting emails at home

2017-12-10 Thread Fabian A. Santiago
On December 10, 2017 2:49:35 PM EST, "André Rodier" wrote: >Hello Mike, > >Yes, I am using a static IP address, but in theory, you could use a >dynamic one. > >Nothing technically would prevent email exchanges between two boxes, as >long as the SPF records are up to date and the