slow mailbox refreshes

[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 message list, 
especially in the one largest 25k+ message folder. is this simply to be 
expected based on my message count or is there some kind of performance 
optimization and tuning i can do to improve the response times?


The mail server itself is a linode hosted VPS:

intel xeon e5-2680 v2 @ 2.80 GHz, 4 cores
8 GB real memory
2 GB virtual memory
200 GB local storage (ext4)
KVM hypervisor

Thanks everyone for any guidance you can offer.


--
Fabian S.

OpenPGP:

0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key)

***

0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)

Re: question about using cram-md5 login passwords

[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 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, will
>it still work? or must they always from this point on use encrypted
>passwords? Thanks. 
>
>Do not use CRAM-MD5/DIGEST-MD5 mechanisms if you are using SSL/TLS
>connection. PLAIN/LOGIN is usually sufficiently secure over encrypted
>transport, and STARTTLS is required over plaintext port too.
>
>In general, CRAM-MD5 is designed to authenticate over insecure
>transport.
>
>Aki
>
>> 
>> --
>> 
>> Thanks,
>> 
>> Fabian S.
>> 
>> OpenPGP:
>> 
>> 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key)
>> 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired / revoked)

Ok I am using tls and have always been doing so. So I'll leave it alone then. 
Thanks for your thoughts. 
--

Fabian A. Santiago

OpenPGP:

0x643082042dc83e6d94b86c405e3daa18a1c22d8f (current key)
 0x3c3fa072accb7ac5db0f723455502b0eeb9070fc (to be retired / revoked)

question about using cram-md5 login passwords

[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, will it still work? or must they always from 
this point on use encrypted passwords? Thanks. 

--

Thanks,

Fabian S.

OpenPGP:

0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key)
0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired / revoked)

Re: 2.3.1 from ghettoforge-testing causes auth failures

[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
>
>I needed it back up so I downgraded (immediately prior version also
>from @gf-testing) and I was fine.
>
>Centos 7.4
>
>I can plan some testing / debug logging time if anyone wishes. 
>
>My doveconf -n is here:
>
>https://pastebin.com/WVV9JFkT
>
>Thanks.
>
>
>--
>
>Thanks,
>
>Fabian S.
>
>OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Resending due to msg not appearing after original send to list. 
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

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

[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 wrote:
>>>
>>>> i've now completely uninstalled all traces of dovecot and
>reinstalled
>>>> from your repo and still the same issue persists with the same
>>>> errors.
>>>
>>> I'd be interested to know if the dovecot23* packages in GhettoForge
>>> Testing have the same issue:
>>>
>>> http://mirror.ghettoforge.org/distributions/gf/el/7/testing/x86_64
>>>
>>> Peter
>> 
>> ok, the gf dovecot23 packages work and i have my sieve back now. BUT,
>initially it didn't but the dovecot-sieve.log produced a different
>error:
>> 
>> Error: Plugin 'stats' not found from directory /usr/lib64/dovecot
>> 
>> this caused me to re-examine my dovecot.conf and i did have in it on
>the main plugins line:
>> 
>> mail_plugins = " stats quota mailbox_alias acl"
>> 
>> i suspect this was a remnant of my prior dovecot version. so i
>removed stats and now all is working fine. the dovecot community repo
>version's errors never mentioned the stats issue. could that have been
>the cause of my issue all along (Aki?)?
>
>Following the documentation could have helped to void such errors:
>
>https://wiki2.dovecot.org/Upgrading/2.3
>
>System reports not finding required shared libraries is a different
>kind 
>of error and is more likely a packaging mistake (although I haven't 
>checked the RPMs provided by dovecot itself as I am a happy ghettoforge
>
>user since long time).
>
>> Thanks everyone and Peter for mentioning the gf packages.
>
>> Thanks,
>> 
>> Fabian S.

Thank you. I do often cause my own issues and need the mailing lists to bounce 
my thoughts off and get my head around it. Part of my downfall I guess. It's a 
good thing I don't work with Linux professionally. ;-)


--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

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

[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
>> errors.
> 
> I'd be interested to know if the dovecot23* packages in GhettoForge
> Testing have the same issue:
> 
> http://mirror.ghettoforge.org/distributions/gf/el/7/testing/x86_64
> 
> Peter

ok, the gf dovecot23 packages work and i have my sieve back now. BUT, initially 
it didn't but the dovecot-sieve.log produced a different error:

Error: Plugin 'stats' not found from directory /usr/lib64/dovecot

this caused me to re-examine my dovecot.conf and i did have in it on the main 
plugins line:

mail_plugins = " stats quota mailbox_alias acl"

i suspect this was a remnant of my prior dovecot version. so i removed stats 
and now all is working fine. the dovecot community repo version's errors never 
mentioned the stats issue. could that have been the cause of my issue all along 
(Aki?)?

Thanks everyone and Peter for mentioning the gf packages. 

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

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

[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" 
>>> <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" 
>>> <fsanti...@garbage-juice.com> wrote:
>>> 
>>> 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:
>>> 
>>> Can you enable mail_debug=yes and provide logs when mail is delivered?
>>> 
>>> Dec 28 12:05:07 mail roundcube:  PHP Error: Unable to connect to 
>>> managesieve on
>>> 127.0.0.1:4190 in 
>>> /var/www/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php
>>> on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve)
>>> Dec 28 12:05:07 mail roundcube: ERROR: Not currently in AUTHORISATION state 
>>> (1)
>>> Dec 28 12:05:07 mail httpd: ERROR: Failed to write to socket: connection 
>>> lost ()
>>> 
>>> This appears to be problem with managesieved, not sieve filters.
>>> 
>>> Now I'm willing to consider the possibility that the RC plugin doesn't work 
>>> with v2.3.0 of dovecot
>>> sieve but why wouldn't my current sieve filters be functional?
>>> 
>>> --
>>> 
>>> Thanks,
>>> 
>>> Fabian S.
>>> 
>>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>>> 
>>> no, i believe it's in dovecot. upon further inspection, dovecot.log reports:
>>> 
>>> mail dovecot: master: Error: service(managesieve-login): command startup 
>>> failed, throttling for 4
>>> secs
>>> 
>>> dovecot-sieve.log reports:
>>> 
>>> mail dovecot: managesieve-login: Fatal: master: service(managesieve-login): 
>>> child 5988 returned
>>> error 127
>>> Dec 28 12:04:07 mail dovecot: managesieve-login: Error: 
>>> dovecot/managesieve-login: error while
>>> loading shared libraries: libdovecot-login.so.0: cannot open shared object 
>>> file: No such file or
>>> directory
>>> 
>>> do you still need the debug logs?
>>> 
>>> --
>>> 
>>> Thanks,
>>> 
>>> Fabian S.
>>> 
>>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>> 
>> Uh, this looks like botched install. Do you have mixed both self-compiled 
>> and packaged version or
>> something?
>> 
>> Aki
> 
> no; it was originally installed on a bare minimal install of centos from the 
> default repos (I had
> probably also added epel beforehand so whichever dovecot comes from is where 
> it did originally). i
> then added your announced repo and ran yum update.
> 
> your repo site's front page also states to run yum update followed by yum 
> upgrade but on centos 7.4
> yum update suffices and updates your packages. that's what i did.
> 
> I've never self-compiled anything dovecot.
> 
> should i simply reinstall it?
> 
> --
> 
> Thanks,
> 
> Fabian S.
> 
> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

i've now completely uninstalled all traces of dovecot and reinstalled from your 
repo and still the same issue persists with the same errors. 

???



--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

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

[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...@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.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:
>> 
>> Can you enable mail_debug=yes and provide logs when mail is delivered?
>> 
>> Dec 28 12:05:07 mail roundcube:  PHP Error: Unable to connect to 
>> managesieve on
>> 127.0.0.1:4190 in 
>> /var/www/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php
>> on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve)
>> Dec 28 12:05:07 mail roundcube: ERROR: Not currently in AUTHORISATION state 
>> (1)
>> Dec 28 12:05:07 mail httpd: ERROR: Failed to write to socket: connection 
>> lost ()
>> 
>> This appears to be problem with managesieved, not sieve filters.
>> 
>> Now I'm willing to consider the possibility that the RC plugin doesn't work 
>> with v2.3.0 of dovecot
>> sieve but why wouldn't my current sieve filters be functional?
>> 
>> --
>> 
>> Thanks,
>> 
>> Fabian S.
>> 
>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>> 
>> no, i believe it's in dovecot. upon further inspection, dovecot.log reports:
>> 
>> mail dovecot: master: Error: service(managesieve-login): command startup 
>> failed, throttling for 4
>> secs
>> 
>> dovecot-sieve.log reports:
>> 
>> mail dovecot: managesieve-login: Fatal: master: service(managesieve-login): 
>> child 5988 returned
>> error 127
>> Dec 28 12:04:07 mail dovecot: managesieve-login: Error: 
>> dovecot/managesieve-login: error while
>> loading shared libraries: libdovecot-login.so.0: cannot open shared object 
>> file: No such file or
>> directory
>> 
>> do you still need the debug logs?
>> 
>> --
>> 
>> Thanks,
>> 
>> Fabian S.
>> 
>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
> 
> Uh, this looks like botched install. Do you have mixed both self-compiled and 
> packaged version or
> something?
> 
> Aki

no; it was originally installed on a bare minimal install of centos from the 
default repos (I had probably also added epel beforehand so whichever dovecot 
comes from is where it did originally). i then added your announced repo and 
ran yum update. 

your repo site's front page also states to run yum update followed by yum 
upgrade but on centos 7.4 yum update suffices and updates your packages. that's 
what i did. 

I've never self-compiled anything dovecot. 

should i simply reinstall it? 

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

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

[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" 
>>> <fsanti...@garbage-juice.com> wrote:
>>> 
>>> 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:
>>> 
>> 
>> Can you enable mail_debug=yes and provide logs when mail is delivered?
>> 
>>> Dec 28 12:05:07 mail roundcube:  PHP Error: Unable to connect to 
>>> managesieve on
>>> 127.0.0.1:4190 in 
>>> /var/www/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php
>>> on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve)
>>> Dec 28 12:05:07 mail roundcube: ERROR: Not currently in AUTHORISATION state 
>>> (1)
>>> Dec 28 12:05:07 mail httpd: ERROR: Failed to write to socket: connection 
>>> lost ()
>> 
>> This appears to be problem with managesieved, not sieve filters.
>> 
>>> Now I'm willing to consider the possibility that the RC plugin doesn't work 
>>> with v2.3.0 of dovecot
>>> sieve but why wouldn't my current sieve filters be functional?
>>> 
>>> --
>>> 
>>> Thanks,
>>> 
>>> Fabian S.
>>> 
>>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
> 
> no, i believe it's in dovecot. upon further inspection, dovecot.log reports:
> 
> mail dovecot: master: Error: service(managesieve-login): command startup 
> failed, throttling for 4
> secs
> 
> dovecot-sieve.log reports:
> 
> mail dovecot: managesieve-login: Fatal: master: service(managesieve-login): 
> child 5988 returned
> error 127
> Dec 28 12:04:07 mail dovecot: managesieve-login: Error: 
> dovecot/managesieve-login: error while
> loading shared libraries: libdovecot-login.so.0: cannot open shared object 
> file: No such file or
> directory
> 
> do you still need the debug logs?
> 
> --
> 
> Thanks,
> 
> Fabian S.
> 
> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

here are the sieve related debug log entries (from dovecot.log):

Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Pigeonhole version 0.5.0 (d68c23a) initializing
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file storage: Using active Sieve script path: 
/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file storage: Using script storage path: 
/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14//sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file storage: Relative path to sieve storage in active link:
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file storage: Using Sieve script path: 
/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file script: Opened script `managesieve' from 
`/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.sieve'
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file storage: Using Sieve script path: 
/var/vmail/sieve/dovecot.sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: file script: Opened script `dovecot' from 
`/var/vmail/sieve/dovecot.sieve'
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Executed before user's personal Sieve script(1): 
/var/vmail/sieve/dovecot.sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Using the following location for user's Sieve script: 
/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Opening script 1 of 2 from `/var/vmail/sieve/dovecot.sieve'
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Loading script /var/vmail/sieve/dovecot.sieve
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Script binary /var/vmail/sieve/dovecot.svbin successfully loaded
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: binary save: not saving binary /var/vmail/sieve/dovecot.svbin, 
because it is already stored
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Executing script from `/var/vmail/sieve/dovecot.svbin'
Dec 28 13:01:58 mail dovecot: lda()<17543>: 
Debug: sieve: Opening script 2 of 2 from 
`/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.

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

[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.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:
>> 
> 
> Can you enable mail_debug=yes and provide logs when mail is delivered?
> 
>> Dec 28 12:05:07 mail roundcube:  PHP Error: Unable to connect to 
>> managesieve on
>> 127.0.0.1:4190 in 
>> /var/www/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php
>> on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve)
>> Dec 28 12:05:07 mail roundcube: ERROR: Not currently in AUTHORISATION state 
>> (1)
>> Dec 28 12:05:07 mail httpd: ERROR: Failed to write to socket: connection 
>> lost ()
> 
> This appears to be problem with managesieved, not sieve filters.
> 
>> Now I'm willing to consider the possibility that the RC plugin doesn't work 
>> with v2.3.0 of dovecot
>> sieve but why wouldn't my current sieve filters be functional?
>> 
>> --
>> 
>> Thanks,
>> 
>> Fabian S.
>> 
>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

no, i believe it's in dovecot. upon further inspection, dovecot.log reports:

mail dovecot: master: Error: service(managesieve-login): command startup 
failed, throttling for 4 secs


dovecot-sieve.log reports:

mail dovecot: managesieve-login: Fatal: master: service(managesieve-login): 
child 5988 returned error 127
Dec 28 12:04:07 mail dovecot: managesieve-login: Error: 
dovecot/managesieve-login: error while loading shared libraries: 
libdovecot-login.so.0: cannot open shared object file: No such file or directory


do you still need the debug logs?

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

dovecot-pigeonhole problems after upgrade to v2.3.0

[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 roundcube:  PHP Error: Unable to connect to 
managesieve on 127.0.0.1:4190 in 
/var/www/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php 
on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve)
Dec 28 12:05:07 mail roundcube: ERROR: Not currently in AUTHORISATION state (1)
Dec 28 12:05:07 mail httpd: ERROR: Failed to write to socket: connection lost ()

Now I'm willing to consider the possibility that the RC plugin doesn't work 
with v2.3.0 of dovecot sieve but why wouldn't my current sieve filters be 
functional? 

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: 2.3.0 upgrade from 2.2.x

[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", 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? Just confirming. Thanks. 
>
>What I mean is doing the -n to a new file hasn't changed or removed
>anything from my old config? Unless it was a changed or obsoleted
>option and in that case it would have warned me anyway, correct? 
>--
>
>Thanks,
>
>Fabian S.
>
>OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC


--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

2.3.0 upgrade from 2.2.x

[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? Just confirming. 
Thanks. 

What I mean is doing the -n to a new file hasn't changed or removed anything 
from my old config? Unless it was a changed or obsoleted option and in that 
case it would have warned me anyway, correct? 
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: Package repository now available

[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"
><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/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 wrote:
>> > >> 
>> > >> Dovecot now has package repository for Debian, CentOS and Ubuntu
>available at
>> > >> https://repo.dovecot.org
>> > >> 
>> > >> Packages are provided for 2.3 series and forward. Please let us
>know if you run into any trouble
>> > >> with these.
>> > >> 
>> > >> ---
>> > >> Aki Tuomi
>> > >> Dovecot oy
>> > >> ___
>> > >> Dovecot-news mailing list
>> > >> dovecot-n...@dovecot.org
>> > >> https://dovecot.org/mailman/listinfo/dovecot-news
>> > 
>> > so i received this (centos 7.4):
>> > 
>> > Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
>> > Importing GPG key 0xED409DA1:
>> >  Userid : "Dovecot Community Edition <dovecot...@dovecot.org>"
>> >  Fingerprint: 2be7 4aab 3ee7 54df b9c8 0d33 18a3 48ae ed40 9da1
>> >  From   : https://repo.dovecot.org/DOVECOT-REPO-GPG
>> > Is this ok [y/N]: y
>> > warning:
>/var/cache/yum/x86_64/7/dovecot-2.3-latest/packages/dovecot-pgsql-2.3.0-2.x86_64.rpm:
>Header V3 DSA/SHA256 Signature, key ID eed949f0: NOKEY
>> > Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
>> > 
>> > 
>> > The GPG keys listed for the "RHEL 7 - x86_64" repository are
>already installed but they are not correct for this package.
>> > Check that the correct key URLs are configured for this repository.
>> > 
>> > 
>> >  Failing package is: 2:dovecot-pgsql-2.3.0-2.x86_64
>> >  GPG Keys are configured as:
>https://repo.dovecot.org/DOVECOT-REPO-GPG
>> > 
>> > 
>> > upgrading from dovecot 2.2.x. 
>> > 
>> > is this related to what you just mentioned with the gpg key? 
>> > 
>> > --
>> > 
>> > Thanks,
>> > 
>> > Fabian S.
>> > 
>> > OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>> 
>> Nope. The amendment was only for debian & ubuntu users.
>> 
>> We'll check why it says NOKEY. It should have been signed.
>> 
>> Aki
>
>Should be fixed now.
>
>Aki

Thank you. Confirmed works ok. 
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: Package repository now available

[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/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 wrote:
>>> 
>>> Dovecot now has package repository for Debian, CentOS and Ubuntu available 
>>> at
>>> https://repo.dovecot.org
>>> 
>>> Packages are provided for 2.3 series and forward. Please let us know if you 
>>> run into any trouble
>>> with these.
>>> 
>>> ---
>>> Aki Tuomi
>>> Dovecot oy
>>> ___
>>> Dovecot-news mailing list
>>> dovecot-n...@dovecot.org
>>> https://dovecot.org/mailman/listinfo/dovecot-news
> 
> so i received this (centos 7.4):
> 
> Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
> Importing GPG key 0xED409DA1:
> Userid : "Dovecot Community Edition <dovecot...@dovecot.org>"
> Fingerprint: 2be7 4aab 3ee7 54df b9c8 0d33 18a3 48ae ed40 9da1
> From : https://repo.dovecot.org/DOVECOT-REPO-GPG
> Is this ok [y/N]: y
> warning: 
> /var/cache/yum/x86_64/7/dovecot-2.3-latest/packages/dovecot-pgsql-2.3.0-2.x86_64.rpm:
> Header V3 DSA/SHA256 Signature, key ID eed949f0: NOKEY
> Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
> 
> The GPG keys listed for the "RHEL 7 - x86_64" repository are already 
> installed but they are not
> correct for this package.
> Check that the correct key URLs are configured for this repository.
> 
> Failing package is: 2:dovecot-pgsql-2.3.0-2.x86_64
> GPG Keys are configured as: https://repo.dovecot.org/DOVECOT-REPO-GPG
> 
> upgrading from dovecot 2.2.x.
> 
> is this related to what you just mentioned with the gpg key?
> 
> --
> 
> Thanks,
> 
> Fabian S.
> 
> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

probably not; i did a manual rpm --import of the key and still received same 
error. is there an issue with the package signatures and the available key not 
matching? 

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: Package repository now available

[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 wrote:
>> 
>> Dovecot now has package repository for Debian, CentOS and Ubuntu available at
>> https://repo.dovecot.org
>> 
>> Packages are provided for 2.3 series and forward. Please let us know if you 
>> run into any trouble
>> with these.
>> 
>> ---
>> Aki Tuomi
>> Dovecot oy
>> ___
>> Dovecot-news mailing list
>> dovecot-n...@dovecot.org
>> https://dovecot.org/mailman/listinfo/dovecot-news

so i received this (centos 7.4):

Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
Importing GPG key 0xED409DA1:
 Userid : "Dovecot Community Edition "
 Fingerprint: 2be7 4aab 3ee7 54df b9c8 0d33 18a3 48ae ed40 9da1
 From   : https://repo.dovecot.org/DOVECOT-REPO-GPG
Is this ok [y/N]: y
warning: 
/var/cache/yum/x86_64/7/dovecot-2.3-latest/packages/dovecot-pgsql-2.3.0-2.x86_64.rpm:
 Header V3 DSA/SHA256 Signature, key ID eed949f0: NOKEY
Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG


The GPG keys listed for the "RHEL 7 - x86_64" repository are already installed 
but they are not correct for this package.
Check that the correct key URLs are configured for this repository.


 Failing package is: 2:dovecot-pgsql-2.3.0-2.x86_64
 GPG Keys are configured as: https://repo.dovecot.org/DOVECOT-REPO-GPG


upgrading from dovecot 2.2.x. 

is this related to what you just mentioned with the gpg key? 

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: hosting emails at home

[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 December 10, 2017 3:39:05 PM EST, Stephan H <her...@gmail.com>
>wrote:
>> >I have dovecot postfix setup on my home server as well.  I use a
>> >virtual
>> >server in the cloud as my mx record and mail relay and have my home
>> >record
>> >on dynamic dns.  It's really effective.
>> >
>> >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 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 DKIM is properly
>> >setup.
>> >> >
>> >> >Unfortunately, some ISPs are simply blacklisting full range of
>> >private
>> >> >IP addresses just because they are not officials / commercials.
>> >> >
>> >> >Kind regards,
>> >> >André
>> >> >
>> >> >On 10/12/17 19:24, Mike wrote:
>> >> >>
>> >> >> Nice.
>> >> >>
>> >> >> Are you using a static IP in this setup?
>> >> >>
>> >> >> It doesn't seem like it, but wanted to be sure.
>> >> >>
>> >> >> Mike.
>> >> >>
>> >> >> Quoting André Rodier <an...@rodier.me>:
>> >> >>
>> >> >>> Hello everyone,
>> >> >>>
>> >> >>> I have been using Postfix and Dovecot for my personal emails
>for
>> >> >years.
>> >> >>> After being tired of reinstalling my personal mail server many
>> >> >times, I
>> >> >>> am currently writing some Ansible scripts to do it
>automatically.
>> >> >>>
>> >> >>> I obviously checked the other projects, and did not found
>> >anything
>> >> >close
>> >> >>> to what I am looking for, so I am implementing it now.
>> >> >>>
>> >> >>> The final goal is to have a box that once online, would setup
>> >> >itself, by
>> >> >>> creating the certificates, the DKIM keys and update the
>> >appropriate
>> >> >DNS
>> >> >>> records.
>> >> >>>
>> >> >>> This is so far what I have achieved:
>> >> >>> - Automatic generation of certificates using LetsEncrypt
>> >> >>> - Automatic update of the domain entries: imap, smtp, webmail,
>> >etc.
>> >> >>> - Automatic generation of a DKIM keys
>> >> >>> - Automatic update of specific records (MX, SPF, DKIM, etc.)
>> >> >>> - LDAP server for user accounts, with or without system login.
>> >> >>> - Installation of Postfix, Dovecot and Roundcube
>> >> >>>
>> >> >>> Sending DKIM signed emails is working, and the IMAP server is
>> >> >configured
>> >> >>> as well, although basic.
>> >> >>>
>> >> >>> The postfix and dovecot configuration are not yet entirely
>> >finished.
>> >> >I
>> >> >>> am planing to add an anti spam system, and sieve, amongst
>other
>> >> >things.
>> >> >>>
>> >> >>> Although in development during my spare time, the system is
>> >normally
>> >> >>> robust and you should be able to run it multiple times without
>> >> >errors.
>> >> >>>
>> >> >>> If anyone is interested to use it, to have a look, or to take
>> >part,
>> >> >it
>> >> >>> is here: https://github.com/progmaticltd/homebox
>> >> >>>
>> >> >>> Kind regards,
>> >> >>> André Rodier.
>> >> >>
>> >> >>
>> >>
>> >> Non static ip'd mail servers are also blocked because they're
>> >typically
>> >> spammers.
>> >> --
>> >>
>> >> Thanks,
>> >>
>> >> Fabian S.
>> >>
>> >> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>> >>
>>
>> Stephan h, may I ask why you do that? Just out of curiosity.
>> --
>>
>> Thanks,
>>
>> Fabian S.
>>
>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>>

Both; the whole setup.
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: hosting emails at home

[Fabian A. Santiago]

On December 10, 2017 3:39:05 PM EST, Stephan H <her...@gmail.com> wrote:
>I have dovecot postfix setup on my home server as well.  I use a
>virtual
>server in the cloud as my mx record and mail relay and have my home
>record
>on dynamic dns.  It's really effective.
>
>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 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 DKIM is properly
>setup.
>> >
>> >Unfortunately, some ISPs are simply blacklisting full range of
>private
>> >IP addresses just because they are not officials / commercials.
>> >
>> >Kind regards,
>> >André
>> >
>> >On 10/12/17 19:24, Mike wrote:
>> >>
>> >> Nice.
>> >>
>> >> Are you using a static IP in this setup?
>> >>
>> >> It doesn't seem like it, but wanted to be sure.
>> >>
>> >> Mike.
>> >>
>> >> Quoting André Rodier <an...@rodier.me>:
>> >>
>> >>> Hello everyone,
>> >>>
>> >>> I have been using Postfix and Dovecot for my personal emails for
>> >years.
>> >>> After being tired of reinstalling my personal mail server many
>> >times, I
>> >>> am currently writing some Ansible scripts to do it automatically.
>> >>>
>> >>> I obviously checked the other projects, and did not found
>anything
>> >close
>> >>> to what I am looking for, so I am implementing it now.
>> >>>
>> >>> The final goal is to have a box that once online, would setup
>> >itself, by
>> >>> creating the certificates, the DKIM keys and update the
>appropriate
>> >DNS
>> >>> records.
>> >>>
>> >>> This is so far what I have achieved:
>> >>> - Automatic generation of certificates using LetsEncrypt
>> >>> - Automatic update of the domain entries: imap, smtp, webmail,
>etc.
>> >>> - Automatic generation of a DKIM keys
>> >>> - Automatic update of specific records (MX, SPF, DKIM, etc.)
>> >>> - LDAP server for user accounts, with or without system login.
>> >>> - Installation of Postfix, Dovecot and Roundcube
>> >>>
>> >>> Sending DKIM signed emails is working, and the IMAP server is
>> >configured
>> >>> as well, although basic.
>> >>>
>> >>> The postfix and dovecot configuration are not yet entirely
>finished.
>> >I
>> >>> am planing to add an anti spam system, and sieve, amongst other
>> >things.
>> >>>
>> >>> Although in development during my spare time, the system is
>normally
>> >>> robust and you should be able to run it multiple times without
>> >errors.
>> >>>
>> >>> If anyone is interested to use it, to have a look, or to take
>part,
>> >it
>> >>> is here: https://github.com/progmaticltd/homebox
>> >>>
>> >>> Kind regards,
>> >>> André Rodier.
>> >>
>> >>
>>
>> Non static ip'd mail servers are also blocked because they're
>typically
>> spammers.
>> --
>>
>> Thanks,
>>
>> Fabian S.
>>
>> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>>

Stephan h, may I ask why you do that? Just out of curiosity. 
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Re: hosting emails at home

[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 DKIM is properly setup.
>
>Unfortunately, some ISPs are simply blacklisting full range of private
>IP addresses just because they are not officials / commercials.
>
>Kind regards,
>André
>
>On 10/12/17 19:24, Mike wrote:
>> 
>> Nice.
>> 
>> Are you using a static IP in this setup?
>> 
>> It doesn't seem like it, but wanted to be sure.
>> 
>> Mike.
>> 
>> Quoting André Rodier :
>> 
>>> Hello everyone,
>>>
>>> I have been using Postfix and Dovecot for my personal emails for
>years.
>>> After being tired of reinstalling my personal mail server many
>times, I
>>> am currently writing some Ansible scripts to do it automatically.
>>>
>>> I obviously checked the other projects, and did not found anything
>close
>>> to what I am looking for, so I am implementing it now.
>>>
>>> The final goal is to have a box that once online, would setup
>itself, by
>>> creating the certificates, the DKIM keys and update the appropriate
>DNS
>>> records.
>>>
>>> This is so far what I have achieved:
>>> - Automatic generation of certificates using LetsEncrypt
>>> - Automatic update of the domain entries: imap, smtp, webmail, etc.
>>> - Automatic generation of a DKIM keys
>>> - Automatic update of specific records (MX, SPF, DKIM, etc.)
>>> - LDAP server for user accounts, with or without system login.
>>> - Installation of Postfix, Dovecot and Roundcube
>>>
>>> Sending DKIM signed emails is working, and the IMAP server is
>configured
>>> as well, although basic.
>>>
>>> The postfix and dovecot configuration are not yet entirely finished.
>I
>>> am planing to add an anti spam system, and sieve, amongst other
>things.
>>>
>>> Although in development during my spare time, the system is normally
>>> robust and you should be able to run it multiple times without
>errors.
>>>
>>> If anyone is interested to use it, to have a look, or to take part,
>it
>>> is here: https://github.com/progmaticltd/homebox
>>>
>>> Kind regards,
>>> André Rodier.
>> 
>> 

Non static ip'd mail servers are also blocked because they're typically 
spammers. 
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC