rename dirs at file system to strip .INBOX prefix?
looking at my personal email in /var/vmail/vmail1/dom.tld/voy...@dom.tld/Maildir I have some older dirs prefixed with .INBOX as so: .INBOX.Sent.2010.11 .INBOX.Sent.2010.12 around 30 or so, every other dir, .Sent or otherwise, doesn't have INBOX prefix can I just rename them from terminal to strip .INBOX from dir name..? and, if I do, what else I need to do or is that a bad idea, if so, how to get rid of old '.INBOX' prefixes? thanks, -- Voytek
Re: Package repository now available
On 2017-12-27 07:00, 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 So what options the package configured with? Does it include "--with-mysql" and "--with-solr"? Thanks. Gao
Re: dovecot-pigeonhole problems after upgrade to v2.3.0
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
Re: dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 2:52 PM, "Fabian A. Santiago" wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" >>> wrote: >>> >>> December 28, 2017 12:14 PM, "Aki Tuomi" wrote: >>> >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >>> 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
December 28, 2017 1:21 PM, "Aki Tuomi" wrote: >> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" >> wrote: >> >> December 28, 2017 12:14 PM, "Aki Tuomi" wrote: >> >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >> 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
> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" > wrote: > > > December 28, 2017 12:14 PM, "Aki Tuomi" wrote: > > >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" > >> 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
Re: dovecot-pigeonhole problems after upgrade to v2.3.0
> On December 28, 2017 at 8:07 PM "Fabian A. Santiago" > wrote: > > > December 28, 2017 12:43 PM, "Fabian A. Santiago" > wrote: > > > December 28, 2017 12:14 PM, "Aki Tuomi" wrote: > > > >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" > >>> 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.sieve' > Dec 28 13:01:58 mail dovecot: lda()<17543>: > Debug: sieve: Loading 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: Script binary > /var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.svbin > successfully loaded >
Re: dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 12:43 PM, "Fabian A. Santiago" wrote: > December 28, 2017 12:14 PM, "Aki Tuomi" wrote: > >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >>> 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.sieve' Dec 28 13:01:58 mail dovecot: lda()<17543>: Debug: sieve: Loading 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: Script binary /var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.svbin successfully loaded Dec 28 13:01:58 mail dovecot: lda()<17543>: Debug: sieve: binary save: not saving binary /var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/sieve/dovecot.svbin, because it is already stored Dec 28 13:01:58 mail dovecot: lda()<17543>: Debug: sieve: Executing script from `/var/vmail/vmail1//f/s/a/-2017.04.06.18.50.14/si
Re: dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 12:14 PM, "Aki Tuomi" wrote: >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >> 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
Re: dovecot-pigeonhole problems after upgrade to v2.3.0
> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" > 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
dovecot-pigeonhole problems after upgrade to v2.3.0
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: doveconf -n not showing all changes
Sorry for the noise, local.conf wasn't readable by a normal user, so it
wasn't tried (!include vs !include_try)
Marc
Marc Weustink wrote:
Hi,
Today I was testing the last dovecot release 2.3 from the dovecot repo
on ubuntu 16.04. (I upgraded from 2.2.23)
I cannot recall if I noticed it before, but doveconf -n not showing all
changes.
To be able to track my changes, I don't touch the config files provided
in conf.d/ anymore, but I write them in local.conf (I did in the past so
doveconf -n still shows something)
I was testing the new submission service so I added to local.conf:
protocols = imap pop3 lmtp sieve submission
service submission-login {
inet_listener submission {
# test
port = 588
}
}
submission_relay_host = 127.0.0.1
after restarting dovecot, submission works, mails get relayed. However
doveconf -n shows:
protocols = imap pop3 lmtp sieve
This is very confusing.
Marc
doveconf -n not showing all changes
Hi,
Today I was testing the last dovecot release 2.3 from the dovecot repo
on ubuntu 16.04. (I upgraded from 2.2.23)
I cannot recall if I noticed it before, but doveconf -n not showing all
changes.
To be able to track my changes, I don't touch the config files provided
in conf.d/ anymore, but I write them in local.conf (I did in the past so
doveconf -n still shows something)
I was testing the new submission service so I added to local.conf:
protocols = imap pop3 lmtp sieve submission
service submission-login {
inet_listener submission {
# test
port = 588
}
}
submission_relay_host = 127.0.0.1
after restarting dovecot, submission works, mails get relayed. However
doveconf -n shows:
protocols = imap pop3 lmtp sieve
This is very confusing.
Marc
Re: Problem with master password
> On 28 Dec 2017, at 13.46, Harald Leithner wrote:
>
> }
> passdb {
> args = /etc/dovecot/master-users
> driver = passwd-file
> master = yes
> pass = yes
> }
> passdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
the default behaviour for first passdb is:
result_success = return-ok, so the second passdb is skipped if authentication
was successfull.
I guess you return some user specific variables from the second passdb which
makes INBOX
unaccessible with master login as dovecot does not know mailbox location.
maybe you should add result_success = continue-ok to the first passdb so that
second passdb
is processed even if master authentication was a success.
Sami
Problem with master password
Hi,
I have a problem using the master password feature of dovecot.
I'm able to login with the password but then dovecot can't select the INBOX.
IMAP test:
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=SCRAM-SHA-1
AUTH=CRAM-MD5] ITronic Mail Store
a login u...@itronic.at*admin password
a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS
THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH
ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE NOTIFY
QUOTA ACL RIGHTS=texk] Logged in
a list "" "%"
* LIST (\HasNoChildren) "/" INBOX
a OK List completed (0.003 + 0.000 + 0.003 secs).
a select INBOX
a NO [SERVERBUG] Internal error occurred. Refer to server log for more
information. [2017-12-28 12:32:41] (0.001 + 0.000 secs).
The log with mail debuging doesn't tell me much:
2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(u...@itronic.at):
Debug: INBOX: Mailbox opened because: SELECT
2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(u...@itronic.at):
Debug: acl vfile: file
/srv/storage1/vmail/itronic/6/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-acl
not found
2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(u...@itronic.at):
Debug: acl vfile: file
/srv/storage1/vmail/itronic/6/mdbox/mailboxes/dovecot-acl not found
2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(u...@itronic.at):
Debug: Namespace : Using permissions from
/srv/storage1/vmail/itronic/6/mdbox: mode=0700 gid=default
2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(u...@itronic.at):
Error: Opening INBOX failed: Mailbox doesn't exist: INBOX
If I use the password of the user it works without problems, I also
tested other users, they have the same problem.
dovecot -n
# 2.2.devel (5af0c9f): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.devel (6c95b56)
# OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.10
auth_cache_negative_ttl = 1 secs
auth_cache_size = 10 M
auth_cache_ttl = 1 secs
auth_master_user_separator = *
auth_mechanisms = PLAIN LOGIN DIGEST-MD5 SCRAM-SHA-1 CRAM-MD5 APOP
auth_verbose = yes
default_client_limit = 600
default_vsz_limit = 512 M
dict {
lastlogin = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
sqlacl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
disable_plaintext_auth = no
first_valid_gid = 1001
first_valid_uid = 1001
hostname = mailsto...@itronic.at
imap_hibernate_timeout = 1 mins
imap_id_log = *
imap_id_send = *
imap_idle_notify_interval = 10 mins
imap_logout_format = bytes=%i/%o
instance_name = mailstore1
last_valid_gid = 1001
last_valid_uid = 1001
lda_original_recipient_header = X-LDA-Original-To
lmtp_rcpt_check_quota = yes
login_greeting = ITronic Mail Store
login_trusted_networks = x.y.z.0/24
mail_attachment_dir = /srv/storage1/vmail_sis
mail_attachment_hash = %{sha512}
mail_attachment_min_size = 64 k
mail_cache_min_mail_count = 5
mail_gid = vmail
mail_location = mdbox:~/mdbox
mail_plugins = zlib lazy_expunge stats acl quota mail_log notify
mail_prefetch_count = 100
mail_server_admin = mailto:postmas...@itronic.at
mail_server_comment = ITronic Mail System
mail_shared_explicit_inbox = yes
mail_uid = vmail
mailbox_list_index = yes
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart
extracttext vacation-seconds
mdbox_preallocate_space = yes
namespace {
hidden = yes
list = no
location =
mdbox:~/mdbox:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index
prefix = "#EXPUNGED/"
subscriptions = no
type = private
}
namespace {
list = children
location = mdbox:%%h/mdbox
prefix = "#Users/%%u/"
separator = /
subscriptions = yes
type = shared
}
namespace inbox {
hidden = no
inbox = yes
location =
mailbox Archvie {
special_use = \Archive
}
mailbox Drafts {
special_use = \Drafts
}
mailbox Sent {
special_use = \Sent
}
mailbox Spam {
special_use = \Junk
}
mailbox Trash {
special_use = \Trash
}
prefix =
separator = /
subscriptions = yes
type = private
}
passdb {
args = /etc/dovecot/master-users
driver = passwd-file
master = yes
pass = yes
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
acl = vfile
acl_shared_dict = proxy::sqlacl
last_login_dict = proxy::lastlogin
last_login_key = last-login/%u
lazy_expunge = "#EXPUNGED/"
lazy_expunge_only_last_instance = no
mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename flag_change save mailbox_create
mail_log_fields = uid box msgid size flags vsize from subject
quot
Re: Ubuntu Auth Issues with new repository code..
> On December 28, 2017 at 12:39 AM Noel Butler wrote: > > > On 28/12/2017 07:38, Howard Leadmon wrote: > > > Saw the new repository notification, and figured what the heck I would try > > letting it upgrade me from the current v2.2.22 release that apparently is > > in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. > > > > I followed the info on repo.dovecot.org, and first it started bitching > > about lmtp (dovecot: master: Fatal: service(lmtp) > > access(/usr/lib/dovecot/lmtp) failed: No such file or directory), so I went > > back and installed the dovecot-lmtpd package and that seemed to fix that > > issue. Just FYI, I had dovecot-core, dovecot-imapd, and dovecot-pop3d > > installed on the system. > > > > OK, so now it started up, said it was 2.3.0 and I thought all was good, but > > now all authentication is failing. I turned on some of the logging > > debugging, and am seeing the below: > > > > dovecot: auth-worker(19578): Debug: > > pam(toss1,127.0.0.1,): lookup service=dovecot > > dovecot: auth-worker(19578): Debug: > > pam(toss1,127.0.0.1,): #1/1 style=1 msg=Password: > > dovecot: auth-worker(19578): pam(toss1,127.0.0.1,): > > pam_authenticate() failed: System error > > dovecot: auth: Debug: client passdb out: FAIL#0111#011user=toss1 > > dovecot: imap-login: Aborted login (auth failed, 1 attempts in 3 secs): > > user=, method=PLAIN, rip=127.0.0.1, lip=127.0.1.1, > > session= > > > > I took and compared my auth files like 10-auth.conf, and > > auth-system.conf.ext, and they are identical between the two versions, even > > though they were overwritten as part of the upgrade. > > > > If I just uninstall the 2.3.0 release, and install 2.2.22 back on the > > server, it all just starts working again.So for now I am back on 2.2, > > but was willing to give 2.3 a run if I can get it going. Any ideas as to > > what to look at to get this working, would be great. As stated above, > > this is Ubuntu Server 16.04.03, and I am also running Postfix and > > amavis-new, but don't think they should really impact me using dovecot for > > email over POP3 or IMAP.. > > > > --- > > Howard Leadmon > > PBW Communications, LLC > > http://www.pbwcomm.com > > Why on earth you think you could upgrade versions by using two unrelated > and different repo's is beyond me. > > This has always been a problem, even back in the 90's with the RPMs, RH > v say for example Fresh, because package maintainers will package > differently. > > Its like trying to stick a cisco 1800 image on an ASR9K and expecting it > to work perfectly. > > Though we don't use deb or rpm based systems and haven't for about 15 > years, if I was to, I think I'd be using the creators version, and not a > distro's version. > > -- > Kind Regards, > > Noel Butler Noel, we have actually tried to make the packages compatible with distros so that the upgrade would work. In general I agree with you, but in this case we did actually take the extra effort to see that they would be reasonably compatible with debian/ubuntu/centos packages. That said, the upgrade is a major version change, so things might be different. Expecting that things "Just Work" is bit too much. https://wiki2.dovecot.org/Upgrading/2.3 should help figuring out what needs to be checked. Aki
