from:"Mike"


OSX 10.13.6 High Sierra, dovecot 2.3.2.1

dovecot starts up and runs but dies as soon as my mail client makes a 
request with log and config below.


And advice appreciated.

Thanks

Mike



20180810-083730 auth: Debug: auth client connected (pid=77432)

20180810-083730 auth: Debug: client in: AUTH    1    PLAIN 
service=imap    secured    session=xo1p2BRzZNd/AAAB lip=127.0.0.1    
rip=127.0.0.1    lport=143    rport=55140

20180810-083730 auth: Debug: client passdb out: CONT    1
20180810-083730 auth: Debug: client in: CONT    1 AG1rbQBta20xMjM= 
(previous base64 data may contain sensitive data)
20180810-083730 auth: Debug: static(mkm,127.0.0.1,): 
lookup
20180810-083730 auth: Debug: client passdb out: OK    1 user=mkm    
host=localhost    nopasswd=y
20180810-083730 auth: Debug: master in: REQUEST    4201906177 77432    
1    b8126b4b71be2959fc7716888eccc566 session_pid=77433    
request_auth_token
20180810-083730 auth-worker(77426): Debug: 
passwd(mkm,127.0.0.1,): lookup
20180810-083730 auth: Debug: master userdb out: USER 4201906177    
mkm    system_groups_user=mkm    uid=503 gid=20    home=/Users/mkm 
auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49
20180810-083730 imap-login: Info: Login: user=, method=PLAIN, 
rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, 
session=
20180810-083730 imap(mkm)<77433>: Fatal: 
setgroups(505) failed: Too many extra groups


# doveconf -n
# 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf
# OS: Darwin 17.7.0 x86_64
# Hostname: pine
auth_debug = yes
auth_debug_passwords = yes
default_internal_user = _dovecot
default_login_user = _dovenull
disable_plaintext_auth = no
listen = 127.0.0.1
log_path = /var/log/dovecot
log_timestamp = "%Y%m%d-%H%M%S "
mail_debug = yes
mail_gid = staff
mail_location = mbox:~/Mail:INBOX=/var/mail/%u
mail_privileged_group = mail
mail_uid = _dovecot
passdb {
  args = password=*** host=localhost nopasswd=y
  driver = static
}
passdb {
  args = login
  driver = pam
}
protocols = imap
service auth {
  user = root
}
service imap-login {
  inet_listener imap {
    address = *
    port = 143
  }
}
ssl = no
userdb {
  driver = passwd
}

Re: dying on osx


Maybe an old problem that has resurfaced???

https://bugzilla.samba.org/show_bug.cgi?id=8773

Mike



On 8/10/18 10:54, Aki Tuomi wrote:

I have to see if this is reproducible outside mac.



---
Aki Tuomi
Dovecot oy

 Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 18:46 (GMT+02:00)
To: Aki Tuomi 
Subject: Re: dying on osx

I did find that page and tried a few things there. My config has all of
the settings there except 3:

mail_access_groups = mail
mbox_read_locks = fcntl
mbox_write_locks = fcntl

I add them to my config, restart and get the same abort

20180810-103849 imap(mkm)<79213>: Fatal:
setgroups(mail,505) failed: Too many extra groups

I've tried numerous other settings as well.

Thanks for any further advice

Mike


On 8/10/18 08:45, Aki Tuomi wrote:
> Can you try this config and report back?
>
> 
https://superuser.com/questions/957272/dotlock-permissions-problems-with-dovecot-and-os-x-10-10-3

>
> Aki
>
>> On 10 August 2018 at 16:39 Mike Makuch <1mikemak...@gmail.com> wrote:
>>
>>
>> OSX 10.13.6 High Sierra, dovecot 2.3.2.1
>>
>> dovecot starts up and runs but dies as soon as my mail client makes a
>> request with log and config below.
>>
>> And advice appreciated.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> 20180810-083730 auth: Debug: auth client connected (pid=77432)
>>
>> 20180810-083730 auth: Debug: client in: AUTH    1 PLAIN
>> service=imap    secured    session=xo1p2BRzZNd/AAAB lip=127.0.0.1
>> rip=127.0.0.1    lport=143    rport=55140
>> 20180810-083730 auth: Debug: client passdb out: CONT    1
>> 20180810-083730 auth: Debug: client in: CONT    1 AG1rbQBta20xMjM=
>> (previous base64 data may contain sensitive data)
>> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,):
>> lookup
>> 20180810-083730 auth: Debug: client passdb out: OK    1 user=mkm
>> host=localhost    nopasswd=y
>> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432
>> 1    b8126b4b71be2959fc7716888eccc566 session_pid=77433
>> request_auth_token
>> 20180810-083730 auth-worker(77426): Debug:
>> passwd(mkm,127.0.0.1,): lookup
>> 20180810-083730 auth: Debug: master userdb out: USER 4201906177
>> mkm    system_groups_user=mkm    uid=503 gid=20 home=/Users/mkm
>> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49
>> 20180810-083730 imap-login: Info: Login: user=, method=PLAIN,
>> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured,
>> session=
>> 20180810-083730 imap(mkm)<77433>: Fatal:
>> setgroups(505) failed: Too many extra groups
>>
>> # doveconf -n
>> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf
>> # OS: Darwin 17.7.0 x86_64
>> # Hostname: pine
>> auth_debug = yes
>> auth_debug_passwords = yes
>> default_internal_user = _dovecot
>> default_login_user = _dovenull
>> disable_plaintext_auth = no
>> listen = 127.0.0.1
>> log_path = /var/log/dovecot
>> log_timestamp = "%Y%m%d-%H%M%S "
>> mail_debug = yes
>> mail_gid = staff
>> mail_location = mbox:~/Mail:INBOX=/var/mail/%u
>> mail_privileged_group = mail
>> mail_uid = _dovecot
>> passdb {
>>     args = password=*** host=localhost nopasswd=y
>>     driver = static
>> }
>> passdb {
>>     args = login
>>     driver = pam
>> }
>> protocols = imap
>> service auth {
>>     user = root
>> }
>> service imap-login {
>>     inet_listener imap {
>>       address = *
>>       port = 143
>>     }
>> }
>> ssl = no
>> userdb {
>>     driver = passwd
>> }
>>
>>

Re: dying on osx



$ grep dove /etc/passwd /etc/group
/etc/passwd:_dovecot:*:214:6:Dovecot Administrator:/var/empty:/usr/bin/false
/etc/passwd:_dovenull:*:227:227:Dovecot 
Authentication:/var/empty:/usr/bin/false

/etc/group:certusers:*:29:root,_jabber,_postfix,_cyrus,_calendar,_dovecot
/etc/group:_dovenull:*:227:


I'm trying to build on osx so I can try to do some debugging. The 
INSTALL.md says to do:



$ more INSTALL.md
Build Instructions
==

For most people, the usual:

```
./configure
make
sudo make install
```

But there is no configure file. How would I generate the configure file? 
Is it generated? Been a long time since I've done open source C code..


Thanks

Mike


On 8/10/18 11:04, Aki Tuomi wrote:

Is the user member of mail group?



---
Aki Tuomi
Dovecot oy

 Original message ----
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 19:02 (GMT+02:00)
To: Aki Tuomi 
Cc: dovecot@dovecot.org
Subject: Re: dying on osx

Maybe an old problem that has resurfaced???

https://bugzilla.samba.org/show_bug.cgi?id=8773

Mike



On 8/10/18 10:54, Aki Tuomi wrote:

I have to see if this is reproducible outside mac.



---
Aki Tuomi
Dovecot oy

 Original message ----
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 18:46 (GMT+02:00)
To: Aki Tuomi 
Subject: Re: dying on osx

I did find that page and tried a few things there. My config has all of
the settings there except 3:

mail_access_groups = mail
mbox_read_locks = fcntl
mbox_write_locks = fcntl

I add them to my config, restart and get the same abort

20180810-103849 imap(mkm)<79213>: Fatal:
setgroups(mail,505) failed: Too many extra groups

I've tried numerous other settings as well.

Thanks for any further advice

Mike


On 8/10/18 08:45, Aki Tuomi wrote:
> Can you try this config and report back?
>
> 
https://superuser.com/questions/957272/dotlock-permissions-problems-with-dovecot-and-os-x-10-10-3

>
> Aki
>
>> On 10 August 2018 at 16:39 Mike Makuch <1mikemak...@gmail.com> wrote:
>>
>>
>> OSX 10.13.6 High Sierra, dovecot 2.3.2.1
>>
>> dovecot starts up and runs but dies as soon as my mail client makes a
>> request with log and config below.
>>
>> And advice appreciated.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> 20180810-083730 auth: Debug: auth client connected (pid=77432)
>>
>> 20180810-083730 auth: Debug: client in: AUTH    1 PLAIN
>> service=imap    secured    session=xo1p2BRzZNd/AAAB lip=127.0.0.1
>> rip=127.0.0.1    lport=143    rport=55140
>> 20180810-083730 auth: Debug: client passdb out: CONT 1
>> 20180810-083730 auth: Debug: client in: CONT    1 AG1rbQBta20xMjM=
>> (previous base64 data may contain sensitive data)
>> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,):
>> lookup
>> 20180810-083730 auth: Debug: client passdb out: OK    1 user=mkm
>> host=localhost    nopasswd=y
>> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432
>> 1    b8126b4b71be2959fc7716888eccc566 session_pid=77433
>> request_auth_token
>> 20180810-083730 auth-worker(77426): Debug:
>> passwd(mkm,127.0.0.1,): lookup
>> 20180810-083730 auth: Debug: master userdb out: USER 4201906177
>> mkm    system_groups_user=mkm    uid=503 gid=20 home=/Users/mkm
>> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49
>> 20180810-083730 imap-login: Info: Login: user=, method=PLAIN,
>> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured,
>> session=
>> 20180810-083730 imap(mkm)<77433>: Fatal:
>> setgroups(505) failed: Too many extra groups
>>
>> # doveconf -n
>> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf
>> # OS: Darwin 17.7.0 x86_64
>> # Hostname: pine
>> auth_debug = yes
>> auth_debug_passwords = yes
>> default_internal_user = _dovecot
>> default_login_user = _dovenull
>> disable_plaintext_auth = no
>> listen = 127.0.0.1
>> log_path = /var/log/dovecot
>> log_timestamp = "%Y%m%d-%H%M%S "
>> mail_debug = yes
>> mail_gid = staff
>> mail_location = mbox:~/Mail:INBOX=/var/mail/%u
>> mail_privileged_group = mail
>> mail_uid = _dovecot
>> passdb {
>>     args = password=*** host=localhost nopasswd=y
>>     driver = static
>> }
>> passdb {
>>     args = login
>>     driver = pam
>> }
>> protocols = imap
>> service auth {
>>     user = root
>> }
>> service imap-login {
>>     inet_listener imap {
>>       address = *
>>       port = 143
>>     }
>> }
>> ssl = no
>> userdb {
>>     driver = passwd
>> }
>>
>>

Re: dying on osx

I've cloned https://github.com/dovecot/core and tried running autogen.sh 
but it fails:

$ bash autogen.sh
/Users/mkm/src/dovecot/doc
--2018-08-10 11:10:26-- https://www.dovecot.org/tmp/wiki2-export.tar.gz
Resolving www.dovecot.org... 94.237.25.159
Connecting to www.dovecot.org|94.237.25.159|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 427414 (417K) [application/x-gzip]
Saving to: ‘wiki2-export.tar.gz’

wiki2-export.tar.gz 
100%[===>] 
417.40K   432KB/s    in 1.0s

2018-08-10 11:10:28 (432 KB/s) - ‘wiki2-export.tar.gz’ saved [427414/427414]

/Users/mkm/src/dovecot/doc/wiki
glibtoolize: putting auxiliary files in '.'.
glibtoolize: copying file './ltmain.sh'
glibtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
glibtoolize: copying file 'm4/libtool.m4'
glibtoolize: copying file 'm4/ltoptions.m4'
glibtoolize: copying file 'm4/ltsugar.m4'
glibtoolize: copying file 'm4/ltversion.m4'
glibtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:293: installing './compile'
configure.ac:299: installing './config.guess'
configure.ac:300: error: required file './config.rpath' not found
configure.ac:299: installing './config.sub'
configure.ac:11: installing './install-sh'
configure.ac:11: installing './missing'
src/anvil/Makefile.am: installing './depcomp'
autoreconf: automake failed with exit status: 1

Any suggestions on how to build on osx?

Thanks

Mike

On 8/10/18 11:08, Mike Makuch wrote:

$ grep dove /etc/passwd /etc/group
/etc/passwd:_dovecot:*:214:6:Dovecot 
Administrator:/var/empty:/usr/bin/false
/etc/passwd:_dovenull:*:227:227:Dovecot 
Authentication:/var/empty:/usr/bin/false

/etc/group:certusers:*:29:root,_jabber,_postfix,_cyrus,_calendar,_dovecot
/etc/group:_dovenull:*:227:

I'm trying to build on osx so I can try to do some debugging. The 
INSTALL.md says to do:

$ more INSTALL.md
Build Instructions
==

For most people, the usual:

```
./configure
make
sudo make install
```

But there is no configure file. How would I generate the configure 
file? Is it generated? Been a long time since I've done open source C 
code..

Thanks

Mike

On 8/10/18 11:04, Aki Tuomi wrote:

Is the user member of mail group?

---
Aki Tuomi
Dovecot oy

 Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 19:02 (GMT+02:00)
To: Aki Tuomi 
Cc: dovecot@dovecot.org
Subject: Re: dying on osx

Maybe an old problem that has resurfaced???

https://bugzilla.samba.org/show_bug.cgi?id=8773

Mike

On 8/10/18 10:54, Aki Tuomi wrote:

I have to see if this is reproducible outside mac.

---
Aki Tuomi
Dovecot oy

 Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 18:46 (GMT+02:00)
To: Aki Tuomi 
Subject: Re: dying on osx

I did find that page and tried a few things there. My config has all of
the settings there except 3:

mail_access_groups = mail
mbox_read_locks = fcntl
mbox_write_locks = fcntl

I add them to my config, restart and get the same abort

20180810-103849 imap(mkm)<79213>: Fatal:
setgroups(mail,505) failed: Too many extra groups

I've tried numerous other settings as well.

Thanks for any further advice

Mike

On 8/10/18 08:45, Aki Tuomi wrote:
> Can you try this config and report back?
>
> 
https://superuser.com/questions/957272/dotlock-permissions-problems-with-dovecot-and-os-x-10-10-3

>
> Aki
>
>> On 10 August 2018 at 16:39 Mike Makuch <1mikemak...@gmail.com> wrote:
>>
>>
>> OSX 10.13.6 High Sierra, dovecot 2.3.2.1
>>
>> dovecot starts up and runs but dies as soon as my mail client makes a
>> request with log and config below.
>>
>> And advice appreciated.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> 20180810-083730 auth: Debug: auth client connected (pid=77432)
>>
>> 20180810-083730 auth: Debug: client in: AUTH    1 PLAIN
>> service=imap    secured    session=xo1p2BRzZNd/AAAB lip=127.0.0.1
>> rip=127.0.0.1    lport=143    rport=55140
>> 20180810-083730 auth: Debug: client passdb out: CONT    1
>> 20180810-083730 auth: Debug: client in: CONT    1 AG1rbQBta20xMjM=
>> (previous base64 data may contain sensitive data)
>> 20180810-083730 auth: Debug: 
static(mkm,127.0.0.1,):

>> lookup
>> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm
>> host=localhost    nopasswd=y
>> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432
>> 1    b8126b4b71be2959fc7716888eccc566 session_pid=77433
>> request_auth_token
>> 20180810-083730 auth-worker(77426): Debug:
>>

Re: dying on osx

Ok I added the two users _dovecot & _dovenull to mail group, still get 
same error "Too many extra groups"



# grep mail /etc/group /usr/local/etc/dovecot/dovecot.conf
/etc/group:mail:*:6:_teamsserver,_dovecot,_dovenull
/etc/group:_mailman:*:78:
/usr/local/etc/dovecot/dovecot.conf:mail_debug = yes
/usr/local/etc/dovecot/dovecot.conf:mail_gid = mail
/usr/local/etc/dovecot/dovecot.conf:mail_location = 
mbox:~/Mail:INBOX=/var/mail/%u

/usr/local/etc/dovecot/dovecot.conf:mail_privileged_group = mail
/usr/local/etc/dovecot/dovecot.conf:mail_access_groups = mail
/usr/local/etc/dovecot/dovecot.conf:mail_uid = _dovecot

20180810-113132 imap(mkm)<68466>: Fatal: 
setgroups(mail,505) failed: Too many extra groups


Thanks
Mike



On 8/10/18 11:08, Mike Makuch wrote:



$ grep dove /etc/passwd /etc/group
/etc/passwd:_dovecot:*:214:6:Dovecot 
Administrator:/var/empty:/usr/bin/false
/etc/passwd:_dovenull:*:227:227:Dovecot 
Authentication:/var/empty:/usr/bin/false

/etc/group:certusers:*:29:root,_jabber,_postfix,_cyrus,_calendar,_dovecot
/etc/group:_dovenull:*:227:


I'm trying to build on osx so I can try to do some debugging. The 
INSTALL.md says to do:



$ more INSTALL.md
Build Instructions
==

For most people, the usual:

```
./configure
make
sudo make install
```

But there is no configure file. How would I generate the configure 
file? Is it generated? Been a long time since I've done open source C 
code..


Thanks

Mike


On 8/10/18 11:04, Aki Tuomi wrote:

Is the user member of mail group?



---
Aki Tuomi
Dovecot oy

 Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 19:02 (GMT+02:00)
To: Aki Tuomi 
Cc: dovecot@dovecot.org
Subject: Re: dying on osx

Maybe an old problem that has resurfaced???

https://bugzilla.samba.org/show_bug.cgi?id=8773

Mike



On 8/10/18 10:54, Aki Tuomi wrote:

I have to see if this is reproducible outside mac.



---
Aki Tuomi
Dovecot oy

---- Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 18:46 (GMT+02:00)
To: Aki Tuomi 
Subject: Re: dying on osx

I did find that page and tried a few things there. My config has all of
the settings there except 3:

mail_access_groups = mail
mbox_read_locks = fcntl
mbox_write_locks = fcntl

I add them to my config, restart and get the same abort

20180810-103849 imap(mkm)<79213>: Fatal:
setgroups(mail,505) failed: Too many extra groups

I've tried numerous other settings as well.

Thanks for any further advice

Mike


On 8/10/18 08:45, Aki Tuomi wrote:
> Can you try this config and report back?
>
> 
https://superuser.com/questions/957272/dotlock-permissions-problems-with-dovecot-and-os-x-10-10-3

>
> Aki
>
>> On 10 August 2018 at 16:39 Mike Makuch <1mikemak...@gmail.com> wrote:
>>
>>
>> OSX 10.13.6 High Sierra, dovecot 2.3.2.1
>>
>> dovecot starts up and runs but dies as soon as my mail client makes a
>> request with log and config below.
>>
>> And advice appreciated.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> 20180810-083730 auth: Debug: auth client connected (pid=77432)
>>
>> 20180810-083730 auth: Debug: client in: AUTH    1 PLAIN
>> service=imap    secured    session=xo1p2BRzZNd/AAAB lip=127.0.0.1
>> rip=127.0.0.1    lport=143    rport=55140
>> 20180810-083730 auth: Debug: client passdb out: CONT    1
>> 20180810-083730 auth: Debug: client in: CONT    1 AG1rbQBta20xMjM=
>> (previous base64 data may contain sensitive data)
>> 20180810-083730 auth: Debug: 
static(mkm,127.0.0.1,):

>> lookup
>> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm
>> host=localhost    nopasswd=y
>> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432
>> 1    b8126b4b71be2959fc7716888eccc566 session_pid=77433
>> request_auth_token
>> 20180810-083730 auth-worker(77426): Debug:
>> passwd(mkm,127.0.0.1,): lookup
>> 20180810-083730 auth: Debug: master userdb out: USER 4201906177
>> mkm    system_groups_user=mkm    uid=503 gid=20 home=/Users/mkm
>> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49
>> 20180810-083730 imap-login: Info: Login: user=, method=PLAIN,
>> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured,
>> session=
>> 20180810-083730 imap(mkm)<77433>: Fatal:
>> setgroups(505) failed: Too many extra groups
>>
>> # doveconf -n
>> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf
>> # OS: Darwin 17.7.0 x86_64
>> # Hostname: pine
>> auth_debug = yes
>> auth_debug_passwords = yes
>> default_internal_user = _dovecot
>> default_login_user = _dovenull
>> disable_plaintext_auth = no
>> listen = 127.0.0.1
>> log_path = /var/log/dovecot
>> log_

Re: dying on osx

I found and tried this work around on the man page: 
https://www.unix.com/man-page/all/5/ngroups_max/ but I still get the 
same "Too many extra groups" error even when I start dovecot with the 
above program to limit the # of groups. I suspect that dovecot is adding 
a number of groups when it starts up.


I've hacked a work around to get it working for me on my laptop:

diff --git a/src/lib/restrict-access.c b/src/lib/restrict-access.c

@@ -224,7 +224,12 @@ static void fix_groups_list(const struct 
restrict_access_settings *set,


-    if (setgroups(gid_count, gid_list) < 0) {

+    if (setgroups(gid_count > NGROUPS_MAX ? 16 : gid_count, gid_list) < 
0) {

     if (errno == EINVAL) {
         i_fatal("setgroups(%s) failed: Too many extra groups",
             set->extra_groups == NULL ? "" :

and this works.

I'm not sure what the right solution is for a PR. Any suggestions?

Thanks

Mike



On 8/10/18 11:04, Aki Tuomi wrote:

Is the user member of mail group?



---
Aki Tuomi
Dovecot oy

 Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 19:02 (GMT+02:00)
To: Aki Tuomi 
Cc: dovecot@dovecot.org
Subject: Re: dying on osx

Maybe an old problem that has resurfaced???

https://bugzilla.samba.org/show_bug.cgi?id=8773

Mike



On 8/10/18 10:54, Aki Tuomi wrote:

I have to see if this is reproducible outside mac.



---
Aki Tuomi
Dovecot oy

 Original message 
From: Mike Makuch <1mikemak...@gmail.com>
Date: 10/08/2018 18:46 (GMT+02:00)
To: Aki Tuomi 
Subject: Re: dying on osx

I did find that page and tried a few things there. My config has all of
the settings there except 3:

mail_access_groups = mail
mbox_read_locks = fcntl
mbox_write_locks = fcntl

I add them to my config, restart and get the same abort

20180810-103849 imap(mkm)<79213>: Fatal:
setgroups(mail,505) failed: Too many extra groups

I've tried numerous other settings as well.

Thanks for any further advice

Mike


On 8/10/18 08:45, Aki Tuomi wrote:
> Can you try this config and report back?
>
> 
https://superuser.com/questions/957272/dotlock-permissions-problems-with-dovecot-and-os-x-10-10-3

>
> Aki
>
>> On 10 August 2018 at 16:39 Mike Makuch <1mikemak...@gmail.com> wrote:
>>
>>
>> OSX 10.13.6 High Sierra, dovecot 2.3.2.1
>>
>> dovecot starts up and runs but dies as soon as my mail client makes a
>> request with log and config below.
>>
>> And advice appreciated.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> 20180810-083730 auth: Debug: auth client connected (pid=77432)
>>
>> 20180810-083730 auth: Debug: client in: AUTH    1 PLAIN
>> service=imap    secured    session=xo1p2BRzZNd/AAAB lip=127.0.0.1
>> rip=127.0.0.1    lport=143    rport=55140
>> 20180810-083730 auth: Debug: client passdb out: CONT 1
>> 20180810-083730 auth: Debug: client in: CONT    1 AG1rbQBta20xMjM=
>> (previous base64 data may contain sensitive data)
>> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,):
>> lookup
>> 20180810-083730 auth: Debug: client passdb out: OK    1 user=mkm
>> host=localhost    nopasswd=y
>> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432
>> 1    b8126b4b71be2959fc7716888eccc566 session_pid=77433
>> request_auth_token
>> 20180810-083730 auth-worker(77426): Debug:
>> passwd(mkm,127.0.0.1,): lookup
>> 20180810-083730 auth: Debug: master userdb out: USER 4201906177
>> mkm    system_groups_user=mkm    uid=503 gid=20 home=/Users/mkm
>> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49
>> 20180810-083730 imap-login: Info: Login: user=, method=PLAIN,
>> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured,
>> session=
>> 20180810-083730 imap(mkm)<77433>: Fatal:
>> setgroups(505) failed: Too many extra groups
>>
>> # doveconf -n
>> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf
>> # OS: Darwin 17.7.0 x86_64
>> # Hostname: pine
>> auth_debug = yes
>> auth_debug_passwords = yes
>> default_internal_user = _dovecot
>> default_login_user = _dovenull
>> disable_plaintext_auth = no
>> listen = 127.0.0.1
>> log_path = /var/log/dovecot
>> log_timestamp = "%Y%m%d-%H%M%S "
>> mail_debug = yes
>> mail_gid = staff
>> mail_location = mbox:~/Mail:INBOX=/var/mail/%u
>> mail_privileged_group = mail
>> mail_uid = _dovecot
>> passdb {
>>     args = password=*** host=localhost nopasswd=y
>>     driver = static
>> }
>> passdb {
>>     args = login
>>     driver = pam
>> }
>> protocols = imap
>> service auth {
>>     user = root
>> }
>> service imap-login {
>>     inet_listener imap {
>>       address = *
>>       port = 143
>>     }
>> }
>> ssl = no
>> userdb {
>>     driver = passwd
>> }
>>
>>

Re: dovecot and postfix, help?

2018-08-19 Thread Mike Makuch

One tip: for checking whether or not you have access to your vps @
host:port you ought to use netcat or telnet from your localhost:

https://www.digitalocean.com/community/tutorials/how-to-use-netcat-to-establish-and-test-tcp-and-udp-connections-on-a-vps

I frequently use telnet since you can also type in the protocol to a
server (assuming the server expects ascii) and get a response out of it.
E.g.

Type:
$ telnet xyzzy.com 80
Server response:
Trying 104.31.88.30...
Connected to xyzzy.com.
Escape character is '^]'.
Type:
GET / HTTP/1.0
Server response:
XYZZY
content="width=device-width,initial-scale=1,maximum-scale=1" />

You are in a twisty maze of passages, all alike.
[snip]

And yes in this case "curl" would be more a appropriate utility (for
http) but not for other protocols that curl doesn't support.

If you telnet to a port that isn't opened and being listened on:

$ telnet localhost 4321
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying fe80::1...
telnet: connect to address fe80::1: Connection refused
telnet: Unable to connect to remote host

Good day
Mike

On 8/17/18 18:05, Christy S wrote:

Hi all,

First a disclaimer. I have played with linux off and on for years, but
this is my first time trying to run a server completely on my own from
start to finish, well it's on a vps, but still. I'm pretty techie, but
a lot of this stuff is new to me, so I apologize for any *duh!*
questions. That said, I've so far installed dovecot, postfix,
wordpress, and related programs mostly successfully by following
tutorials. I say mostly successfully, because I'm having a really hard
time trying to get dovecot and postfix to behave together, and I'm
about at the end of what I know how to find on google.

If you're still with me and not groaning at yet another newbie asking
wtf did I do wrong questions, thank you! My basic setup is running
ubuntu 18 with up to date dovecot and postfix. Sasl is installed, and
I'm using a custom domain with all records successfully pointing to
the VPS.

As I mentioned, I've been following tutorials. My goal is to have a
mail server which can send and receive emails using this custom domain
both from the shell and, much more often, from my primary computer
using thunderbird. As there will likely only be two of us using this,
I'm completely fine with the setup using mailboxes that actually have
linux accounts. I'm also using maildir as the mailbox type.
Furthermore, I want to make sure to use ssl on any mail connections..
Normal passwords but ssl being used.

So, following one tutorial I set up postfix and dovecot, then went to
test it. The result was that while on the shell, I could send email to
my gmail account from the domain and receive it just fine. I could
also send mail from my gmail account to the domain and receive it on
the shel. I even managed to get imap to work, so I could receive
domain emails in thunderbird, after playing around with tb's settings.
However, if using tb I attempted to send an email using the custom
domain, smtp failed to connect.

I verified with my VPS provider that no, they do not block port 25,
465 or 587. I also verified that at&t, my home ISP, does not block
outgoing smtp traffic, considering I am using google's for my gmail
account. After hitting google again, I realized two things. One, for
some reason port 25 never got opened on UFW, so I fixed that. Second,
for some reason in all the stuff I did, postfix never got configured
to use SSL.

I found yet another tutorial, and ran through it to set up SSL with
postfix. However, in doing this I had to change a path for sasl, only
to find out later that doing that broke dovecot! Imap completely and
utterly stopped behaving.

Back to google again, and this time I found something a bit more up to
date which explained how to interconnect postfix and dovecot. It goes
through using mysql too, but I don't need that, so I skipped that
part. Changed the sasl path back to what it should be, told dovecot
and postfix to talk to each other and... Nope, still nothing.

I saw a warning that I should not use different certificates for
postfix and dovecot, so I told dovecot to look at the smtpd
certificate that I made. Not sure if that's what's breaking this or
something completely different, as I'm also brand new to the ssl
certificate creation process. So, here's the current status of using
thunderbird with my domain.

mail sent from gmail to new domain, never comes back in thunderbird
but doesn't bounce, either.

Mail sent via thunderbird to gmail from domain, works, but shows up as
from my gmail domain as well, which makes me

no shared cipher openssl

2020-11-15 Thread Mike Schroeder

CentOS 7
Dovecot 2.2.36

Nov 14 07:13:08 mail dovecot: pop3-login: Disconnected (no auth attempts in
0 secs):
user=<>, rip=73.0.0.0, lip=192.64.118.242, TLS handshaking: SSL_accept()
failed:
error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher,
session=<>

Was working fine for over a year, until the cert expired and I replaced it.
I've tried the good cert I have for https and I used the Dovecot.org script
to generate a self-signed certificate.

10-ssl.conf
## SSL settings
#ssl = required
ssl = yes
#ssl = no
ssl_cert =

Problem enabling the mail_log plugin

2021-02-07 Thread Mike Quigley

I need to track some issues with deleted messages so I have been trying 
to set up the mail_log plugin.  I have Dovecot v2..27 running on Debian 
9.  I have configured /etc/dovecot/conf.d/10-logging.conf, 20-imap.conf, 
and 20-lmtp.conf and restarted dovecot, but I see so difference in 
/var/log/mail.info & /var/log/syslog when I delete a message from my 
Inbox in Roundcube.  Here is the abbreviated output from doveconf -n:


# 2.2.27 (): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 ()
# OS: Linux 4.9.0-14-amd64 x86_64 Debian 9.13 ext4

plugin {
mail_log_events = delete undelete mailbox_delete mailbox_rename
mail_log_fields = uid box msgid size
sieve = ~/.dovecot.sieve
sieve_after = /etc/dovecot/sieve-after
sieve_dir = ~/sieve
}

protocols = " imap lmtp sieve pop3"

protocol lmtp {
mail_plugins = " sieve notify mail_log"
}

protocol imap {
mail_max_userip_connections = 50
mail_plugins = " notify mail_log"
}

What am I missing?

Re: Problem enabling the mail_log plugin

2021-02-09 Thread Mike Quigley

I looked at the Trash messages on the Server (which is using Maildir) 
and they are flagged as :2,S (Seen) but not T (Trash). So it looks like 
when Roundcube copies them to Trash and expunges the original, it 
doesn't set the Trash flag on the message.  If I manually delete the 
message from the Trash folder, then RC does set the Trash flag and that 
action will be logged to my Dovecot logs. I did not set the expunge & 
copy options in mail_log_events because I didn't want to fill up the 
logs with all that additional logging, thinking that delete would get me 
what I was looking for.  Thanks for pointing me in the right direction.

--

On 2021-02-09 3:44 am, Yassine Chaouche wrote:


Le 2/9/21 à 11:41 AM, Yassine Chaouche a écrit :


I have expunge in mail_log_events

mail_log_events = delete undelete expunge copy mailbox_delete 
mailbox_rename


Yassine

Oh yes and copy, because when you delete mail in roundcube it actually
copies it to the trash then expunge it from where it was, so you
should look after these two

Yassine.

Re: Problem enabling the mail_log plugin

2021-02-09 Thread Mike Quigley

The default Debian 8 or 9 install of Dovecot duplicates Dovecot logging 
in both /var/log/mail.info & /var/log/syslog.  This server was 
originally setup with v8 and later upgraded to v9.

--

On 2021-02-09 3:46 am, Yassine Chaouche wrote:


Le 2/8/21 à 5:03 AM, Mike Quigley a écrit :
I see so difference in /var/log/mail.info & /var/log/syslog


Did you configure it to use syslog ? my config puts dovecot logs in 
/var/log/dovecot


Yassine.

Undefined symbol using fts-flatcurve with repo.dovecot.org packages

2021-12-18 Thread Mike Acar



Hi,

I'm trying to use dovecot-fts-flatcurve with dovecot 2:2.3.15-1+debian10
from repo.dovecot.org, but it looks like the package doesn't include
ICU, which fts-flatcurve requires.

After compilation and installation, I get an error from doveadm:

doveadm fts-flatcurve stats -u user INBOX
Fatal: Couldn't load required plugin
/usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: dlopen() failed:
/usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: undefined
symbol: _ZTIN6icu_638ByteSinkE

Unmangled, I think that's this symbol:

U typeinfo for icu_63::ByteSink

I checked the rules file from dovecot_2.3.15-1%2Bdebian10.debian.tar.xz
and it appears that configure doesn't include --with-icu.

Is there a plan to include this in a future release?

-- 
  | Mike Acar |    | mike at waspfactory dot org |

Re: JMAP support in Dovecot

2020-01-22 Thread Mike Gao

Hi,

Any news for jmap Support in Dovecot?

Thanks,
Mike

public folder subscriptions sync issue with ldap user/group in dovecot-acl

2016-12-13 Thread Mike Fröhner


Hello people,

I am having an issue with 'doveadm sync'. I am currently trying to have 
two dovecots behind an haproxy (works fine). Therefore I configured 
these two dovecot server (imap-1/imap-2) to sync throught dsync. This 
works just partly. The sync of the maiboxes is fine, but the sync of the 
subscriptions file just works partly. It works for private folder 
subscription, but not completly for public folder subscription. I found 
two issues, if I am using LDAP (user/groups) in dovecot ACLs.


1. I would like to subscribe 2 public folder (public/test/test1 and 
public/test/test2).


My user (ldaptestuser) is an ldap user and this user is member of the 
ldap group (ldaptestgroup) which does have all dovecot-acl rights on 
these folders.


imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl
group=ldaptestgroup akxeilprwts
group=ldaptestgroup akxeilprwts

I am now connecting with my mail client to imap-1 (throught haproxy) and 
the subscription to this folder works. The file which is written looks like:


imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1
publictest/test/test2

Now I am awaiting the synch to imap-2, but the file which it written 
looks like:


imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent

If I modify the dovecot-acl for .test1 to

imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl
group=ldaptestgroup akxeilprwts
user=ldaptestuser akxeilprwts

and execute the subscription again - the synced file looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1

The subscription of public folder test2 will also been synced, if I add 
my ldaptestuser to the acl file for this folder.


2. Another issue is to unsubscribe a public folder. If I unsubscribe 
folder test1, it is written to subscriptions file on the imap where I am 
connected, but it is NOT synced even if my user and group are configured 
at the dovecot-acl file. If I then unsubscribe a not public folder (like 
Sent), the former unsubscribed folder test1 is (faulty) subscribed 
again. But both imap do have the same subscriptions for my ldaptestuser 
user.


I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on 
CentOS-7 (selinux disabled).


If you need more information like the dovecot -n or some other stuff 
give me a short notice.


Mike;

Re: public folder subscriptions sync issue with ldap user/group in dovecot-acl

2016-12-14 Thread Mike Fröhner

I made some additional tests and found that also local unix groups are 
not working in replacement for my ldap groups as discribed below.


Do groups in dovecot-acl intendedly not work?

On 12/13/2016 03:47 PM, Mike Fröhner wrote:

Hello people,

I am having an issue with 'doveadm sync'. I am currently trying to have
two dovecots behind an haproxy (works fine). Therefore I configured
these two dovecot server (imap-1/imap-2) to sync throught dsync. This
works just partly. The sync of the maiboxes is fine, but the sync of the
subscriptions file just works partly. It works for private folder
subscription, but not completly for public folder subscription. I found
two issues, if I am using LDAP (user/groups) in dovecot ACLs.

1. I would like to subscribe 2 public folder (public/test/test1 and
public/test/test2).

My user (ldaptestuser) is an ldap user and this user is member of the
ldap group (ldaptestgroup) which does have all dovecot-acl rights on
these folders.

imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl
group=ldaptestgroup akxeilprwts
group=ldaptestgroup akxeilprwts

I am now connecting with my mail client to imap-1 (throught haproxy) and
the subscription to this folder works. The file which is written looks
like:

imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1
publictest/test/test2

Now I am awaiting the synch to imap-2, but the file which it written
looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent

If I modify the dovecot-acl for .test1 to

imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl
group=ldaptestgroup akxeilprwts
user=ldaptestuser akxeilprwts

and execute the subscription again - the synced file looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1

The subscription of public folder test2 will also been synced, if I add
my ldaptestuser to the acl file for this folder.

2. Another issue is to unsubscribe a public folder. If I unsubscribe
folder test1, it is written to subscriptions file on the imap where I am
connected, but it is NOT synced even if my user and group are configured
at the dovecot-acl file. If I then unsubscribe a not public folder (like
Sent), the former unsubscribed folder test1 is (faulty) subscribed
again. But both imap do have the same subscriptions for my ldaptestuser
user.

I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on
CentOS-7 (selinux disabled).

If you need more information like the dovecot -n or some other stuff
give me a short notice.

Mike;

Re: public folder subscriptions sync issue with ldap user/group in dovecot-acl

2016-12-16 Thread Mike Fröhner


Thanks for your reply Timo.

On 12/14/2016 06:40 PM, Timo Sirainen wrote:

On 14 Dec 2016, at 11.16, Mike Fröhner mailto:mikefroeh...@gmx.de>> wrote:


I made some additional tests and found that also local unix groups are
not working in replacement for my ldap groups as discribed below.

Do groups in dovecot-acl intendedly not work?


http://wiki2.dovecot.org/ACL -> ACL groups support works by returning a
comma-separated acl_groups extra field from userdb, which contains all
the groups the user belongs to. User's UNIX groups have no effect on
ACLs (you can "enable" them by using a special post-login script).


I think I have configured the userdb right, because the debug log tells 
me this:


imap-1 dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser
imap-1 dovecot: imap(ldaptestuser): Debug: acl: owner = 1
imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: mailusers
imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup





On 12/13/2016 03:47 PM, Mike Fröhner wrote:

Hello people,

I am having an issue with 'doveadm sync'. I am currently trying to have
two dovecots behind an haproxy (works fine). Therefore I configured
these two dovecot server (imap-1/imap-2) to sync throught dsync. This
works just partly. The sync of the maiboxes is fine, but the sync of the
subscriptions file just works partly. It works for private folder
subscription, but not completly for public folder subscription. I found
two issues, if I am using LDAP (user/groups) in dovecot ACLs.

1. I would like to subscribe 2 public folder (public/test/test1 and
public/test/test2).

My user (ldaptestuser) is an ldap user and this user is member of the
ldap group (ldaptestgroup) which does have all dovecot-acl rights on
these folders.

imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl
group=ldaptestgroup akxeilprwts
group=ldaptestgroup akxeilprwts

I am now connecting with my mail client to imap-1 (throught haproxy) and
the subscription to this folder works. The file which is written looks
like:

imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1
publictest/test/test2

Now I am awaiting the synch to imap-2, but the file which it written
looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent

If I modify the dovecot-acl for .test1 to

imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl
group=ldaptestgroup akxeilprwts
user=ldaptestuser akxeilprwts

and execute the subscription again - the synced file looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1

The subscription of public folder test2 will also been synced, if I add
my ldaptestuser to the acl file for this folder.

2. Another issue is to unsubscribe a public folder. If I unsubscribe
folder test1, it is written to subscriptions file on the imap where I am
connected, but it is NOT synced even if my user and group are configured
at the dovecot-acl file. If I then unsubscribe a not public folder (like
Sent), the former unsubscribed folder test1 is (faulty) subscribed
again. But both imap do have the same subscriptions for my ldaptestuser
user.

I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on
CentOS-7 (selinux disabled).

If you need more information like the dovecot -n or some other stuff
give me a short notice.

Mike;

Re: public folder subscriptions sync issue with ldap user/group in dovecot-acl

2016-12-16 Thread Mike Fröhner


Hi again,

here some more debugs:

On 12/16/2016 03:25 PM, Mike Fröhner wrote:

Thanks for your reply Timo.

On 12/14/2016 06:40 PM, Timo Sirainen wrote:

On 14 Dec 2016, at 11.16, Mike Fröhner mailto:mikefroeh...@gmx.de>> wrote:


I made some additional tests and found that also local unix groups are
not working in replacement for my ldap groups as discribed below.

Do groups in dovecot-acl intendedly not work?


http://wiki2.dovecot.org/ACL -> ACL groups support works by returning a
comma-separated acl_groups extra field from userdb, which contains all
the groups the user belongs to. User's UNIX groups have no effect on
ACLs (you can "enable" them by using a special post-login script).


I think I have configured the userdb right, because the debug log tells
me this:

imap-1 dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser
imap-1 dovecot: imap(ldaptestuser): Debug: acl: owner = 1
imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: mailusers
imap-1 dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup


Well, the IMAP debug lists/adds the groups, but not the doveadm:

Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: auth PASS 
input: user=ldaptestuser
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: auth USER 
input: ldaptestuser home=/opt/mail/ldaptestuser 
mail=maildir:/opt/mail/ldaptestuser/Mails gid=991 uid=834603987
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: Added 
userdb setting: mail=maildir:/opt/mail/ldaptestuser/Mails
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: Effective 
uid=834603987, gid=991, home=/opt/mail/ldaptestuser




Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: Namespace 
public-test: type=public, prefix=public/test/, sep=/, inbox=no, 
hidden=no, list=yes, subscriptions=no 
location=maildir:/opt/mail/_public/test
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: maildir++: 
root=/opt/mail/_public/test, index=, indexpvt=, control=, inbox=, alt=
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl: 
initializing backend with data: vfile
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl: acl 
username = ldaptestuser

Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl: owner = 0
Dec 16 16:36:12 imap-1 dovecot: doveadm(ldaptestuser): Debug: acl vfile: 
Global ACLs disabled


The debug output equals on server imap-1 and imap-2.







On 12/13/2016 03:47 PM, Mike Fröhner wrote:

Hello people,

I am having an issue with 'doveadm sync'. I am currently trying to have
two dovecots behind an haproxy (works fine). Therefore I configured
these two dovecot server (imap-1/imap-2) to sync throught dsync. This
works just partly. The sync of the maiboxes is fine, but the sync of
the
subscriptions file just works partly. It works for private folder
subscription, but not completly for public folder subscription. I found
two issues, if I am using LDAP (user/groups) in dovecot ACLs.

1. I would like to subscribe 2 public folder (public/test/test1 and
public/test/test2).

My user (ldaptestuser) is an ldap user and this user is member of the
ldap group (ldaptestgroup) which does have all dovecot-acl rights on
these folders.

imap-1 # cat /opt/mail/_public/publictest/.test*/dovecot-acl
group=ldaptestgroup akxeilprwts
group=ldaptestgroup akxeilprwts

I am now connecting with my mail client to imap-1 (throught haproxy)
and
the subscription to this folder works. The file which is written looks
like:

imap-1 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1
publictest/test/test2

Now I am awaiting the synch to imap-2, but the file which it written
looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent

If I modify the dovecot-acl for .test1 to

imap-1 # cat /opt/mail/_public/publictest/.test1/dovecot-acl
group=ldaptestgroup akxeilprwts
user=ldaptestuser akxeilprwts

and execute the subscription again - the synced file looks like:

imap-2 # cat /opt/mail/ldaptestuser/Mails/subscriptions
Sent
publictest/test/test1

The subscription of public folder test2 will also been synced, if I add
my ldaptestuser to the acl file for this folder.

2. Another issue is to unsubscribe a public folder. If I unsubscribe
folder test1, it is written to subscriptions file on the imap where
I am
connected, but it is NOT synced even if my user and group are
configured
at the dovecot-acl file. If I then unsubscribe a not public folder
(like
Sent), the former unsubscribed folder test1 is (faulty) subscribed
again. But both imap do have the same subscriptions for my ldaptestuser
user.

I do have the behavior with dovecot-2.2.26 and dovecot-2.2.27 on
CentOS-7 (selinux disabled).

If you need more information like the dovecot -n or some other stuff
give me a short notice.

Mike;

dsync for subscription on public/shared folder

2016-12-22 Thread Mike Fröhner


Hello,

I already wrote regarding that, but maybe it sounded too complex. I will 
write it a bit softer now.


The replication through dsnyc works perfectly with one exception. I am 
having an issue with the replication of the subscriptions file on shared 
folder.


We have a public mailbox defined:

namespace public-test {
  location = maildir:/opt/mail/_public/test
  prefix = public/test/
  separator = /
  subscriptions = no
  type = public
}

There 2 subfolder .Test1 and .Test2 which I would like to subscribe on 
my user "ldaptestuser" which is part of the group "ldaptestgroup"


The dovecot-acl file on /opt/mail/_public/test and 
/opt/mail/_public/test/.Test{1,2} are the same and are containing:


group=ldaptestgroup lrwstipekxa

Now if I login through my client (Thunderbird or Roundcubemail) I can 
see the following debug log:


dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser
dovecot: imap(ldaptestuser): Debug: acl: owner = 0
dovecot: imap(ldaptestuser): Debug: acl: group added: domain users
dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup
dovecot: imap(ldaptestuser): Debug: acl: group added: all_mailuser

I created one new private folder on the mailbox of my test user and also 
subscribed it. This subscription is successfully replicated.


After that I am trying to subscribe the public folder. I can see the 
folder in my client after I subscribed them. But on the 2nd dovecot 
server the subscription file is not updated.


imap-1 # cat subscription
Private1
public/test/Test1

imap-2 # cat subscription
Private1

The debug log on both dovecot server tells me:
dovecot: doveadm(,ldaptestuser): Debug: Effective uid=834603987, 
gid=991, home=/opt/mail/ldaptestuser
dovecot: doveadm(,ldaptestuser): Debug: acl: No acl_shared_dict 
setting - shared mailbox listing is disabled
dovecot: doveadm(,ldaptestuser): Debug: maildir++: 
root=/opt/mail/_public/test, index=, indexpvt=, control=, inbox=, alt=
dovecot: doveadm(,ldaptestuser): Debug: acl: initializing backend 
with data: vfile

dovecot: doveadm(,ldaptestuser): Debug: acl: acl username = ldaptestuser
dovecot: doveadm(,ldaptestuser): Debug: acl: owner = 0
dovecot: doveadm(,ldaptestuser): Debug: acl vfile: Global ACLs disabled

It looks like the doveadm() cannot find the group or is not 
checking/initalizing the groups.


Anybody any idea if I missconfigured something or is this just a bug? I 
really would appreciate some help.


kind regards,
Mike;

Re: dsync for subscription on public/shared folder

2017-01-08 Thread Mike Fröhner

I can
see the following debug log:

dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser
dovecot: imap(ldaptestuser): Debug: acl: owner = 0
dovecot: imap(ldaptestuser): Debug: acl: group added: domain users
dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup
dovecot: imap(ldaptestuser): Debug: acl: group added: all_mailuser

I created one new private folder on the mailbox of my test user and also
subscribed it. This subscription is successfully replicated.

After that I am trying to subscribe the public folder. I can see the
folder in my client after I subscribed them. But on the 2nd dovecot
server the subscription file is not updated.

imap-1 # cat subscription
Private1
public/test/Test1

imap-2 # cat subscription
Private1

The debug log on both dovecot server tells me:
dovecot: doveadm(,ldaptestuser): Debug: Effective uid=834603987,
gid=991, home=/opt/mail/ldaptestuser
dovecot: doveadm(,ldaptestuser): Debug: acl: No acl_shared_dict
setting - shared mailbox listing is disabled
dovecot: doveadm(,ldaptestuser): Debug: maildir++:
root=/opt/mail/_public/test, index=, indexpvt=, control=, inbox=, alt=
dovecot: doveadm(,ldaptestuser): Debug: acl: initializing backend
with data: vfile
dovecot: doveadm(,ldaptestuser): Debug: acl: acl username =
ldaptestuser
dovecot: doveadm(,ldaptestuser): Debug: acl: owner = 0
dovecot: doveadm(,ldaptestuser): Debug: acl vfile: Global ACLs disabled

It looks like the doveadm() cannot find the group or is not
checking/initalizing the groups.

Anybody any idea if I missconfigured something or is this just a bug? I
really would appreciate some help.

kind regards,
Mike;

Re: Replication: Can't unsubscribe from shared mailbox

2017-01-16 Thread Mike Fröhner


Hi Karsten,

I have a similar issue with current 2.2.27 version on CentOS with public 
folder/namespaces on a active/active replication.


I am able to subscribe the public folder on one dovecot, but it is not 
replicated to the 2nd dovecot throught dsync. Everything else is fine 
with dsync, also the replication of the subscription of private/personal 
folder.


Currently I am trying to debug this at the source code, but my C is 
quite dusty.


Mike;

On 01/16/2017 03:19 PM, Karsten Heiken wrote:

Hi all,

I hope it's okay to bump this once after four months.

In the meantime we updated to 2.2.26.0 and our problem still persists:
After unsubscribing from a shared mailbox, the subscription instantly
re-appears.
A pcap was attached to my original mail, in case it has something to do
with dsync:
http://dovecot.org/pipermail/dovecot/2016-September/105419.html

Is anyone on this mailing list using replication in combination with
shared folders?
Does this problem exist for anyone else? I would love to hear from
people who got this working or if anyone else is affected by this.

My original post is at the end of this email; the current doveconf is
also attached.


Thank you very much,

Karsten

# doveconf -n
# 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 (fed8554)
# OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6
auth_cache_size = 10 M
auth_cache_ttl = 2 hours
default_vsz_limit = 1 G
dict {
  acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
lmtp_rcpt_check_quota = yes
login_trusted_networks = xxx
mail_attribute_dict = file:%h/dovecot-attributes
mail_gid = 
mail_location = mdbox:%h/mdbox
mail_plugins = " zlib quota acl notify replication"
mail_server_admin = mailto:postmaster@xxx
mail_server_comment = xxx
mail_shared_explicit_inbox = yes
mail_uid = 
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 imapflags notify
mdbox_rotate_size = 10 M
namespace {
  hidden = no
  ignore_on_failure = no
  inbox = no
  list = children
  location = mdbox:%%h/mdbox:INDEXPVT=%h/shared/%%u
  prefix = shared/%%u/
  separator = /
  subscriptions = no
  type = shared
}
namespace inbox {
  hidden = no
  inbox = yes
  list = yes
  location =
  mailbox 30dTrash {
auto = subscribe
autoexpunge = 30 days
special_use = \Junk
  }
  mailbox Drafts {
auto = subscribe
special_use = \Drafts
  }
  mailbox Sent {
auto = subscribe
special_use = \Sent
  }
  mailbox Trash {
auto = subscribe
special_use = \Trash
  }
  prefix =
  separator = /
  subscriptions = yes
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  acl = vfile
  acl_shared_dict = proxy::acl
  mail_replica = tcp:xxx:24245
  quota = dict:User quota::noenforcing:file:%h/dovecot-quota
  quota_grace = 2%%
  quota_rule = *:storage=8G
  quota_status_nouser = DUNNO
  quota_status_overquota = DUNNO
  quota_status_success = DUNNO
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_extensions = +notify +imapflags
  sieve_max_actions = 250
  sieve_max_redirects = 200
  zlib_save = gz
  zlib_save_level = 6
}
postmaster_address = postmaster@xxx
protocols = " imap lmtp sieve pop3 sieve"
replication_dsync_parameters = -d -l 30 -U -N
replication_max_conns = 5
service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
  }
  unix_listener replication-notify {
user = vmail
  }
}
service auth {
  unix_listener auth-userdb {
group = vmail
user = vmail
  }
}
service dict {
  unix_listener dict {
group = vmail
mode = 0660
user = vmail
  }
}
service doveadm {
  inet_listener {
port = 24245
  }
}
service imap-login {
  process_min_avail = 16
  service_count = 0
}
service imap {
  executable = imap postlogin
  process_limit = 3
}
service lmtp {
  inet_listener lmtp {
port = 24
  }
  vsz_limit = 1 G
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
}
service managesieve {
  process_limit = 1024
}
service pop3-login {
  process_min_avail = 4
  service_count = 0
}
service pop3 {
  process_limit = 2500
}
service postlogin {
  executable = script-login -d rawlog /usr/local/bin/dovecot-postlogin.sh
}
service quota-status {
  client_limit = 1
  executable = quota-status -p postfix
  inet_listener {
port = 12340
  }
}
service replicator {
  process_min_avail = 1
  unix_listener replicator-doveadm {
mode = 0600
user = vmail
  }
}
shutdown_clients = no
ssl_cert = 
Hi,

I am running two dovecot servers active/active.
Everything runs pretty great, except for the replication of
subscriptions in a shared namespace.

When I unsubscribe from a folder the subscription instantly
re-appears. The timestamp on the subs

Re: dsync dovecot / Failed connection refused

2017-01-24 Thread Mike Fröhner


Hello,

I might be wrong, but the port which will be used for the replicator 
port is the value of 'doveadm_port' which in your case is 4711.


Mike;

On 01/23/2017 05:58 PM, Thierry wrote:

Dear all,

I am using VMWare and I  have cloned my emails server.
Now I do have two identicals servers, both running the same version of dovecot 
(2.2.13) and imap.
Let's call them: server1.domain.ltd  and server2.domain.ltd.
I would  like to sync both server using dsync.

Dovecot is working well except concerning  the sync.

dsync config server1.domain.ltd

# Enable the replication plugin globally
mail_plugins = $mail_plugins notify replication

# The mail processes need to have access to the replication-notify fifo and 
socket.
service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
mode = 0666
  }
  unix_listener replication-notify {
user = vmail
mode = 0666
  }
}

# Enable doveadm replicator commands
service replicator {
  unix_listener replicator-doveadm {
mode = 0666
  }
}

# Create a listener for doveadm-server
service doveadm {
  user = vmail
  inet_listener {
port = 12345
  }
}

# configure how many dsyncs can be run in parallel (10 by default)
replication_max_conns = 10

# tell doveadm client to use this port by default
doveadm_port = 4711

#Both the client and the server also need to have a shared secret
doveadm_password = {SHA512-CRYPT}$6$rou
# use tcp:hostname as the dsync target
plugin {
  #mail_replica = tcp:server2.domain.ltd # use doveadm_port
  mail_replica = tcp:server2.domain.ltd:12345 # use port 12345 explicitly
}

service config {
  unix_listener config {
user = vmail
  }
}

***

dsync config server2.domain.ltd

# Enable the replication plugin globally
mail_plugins = $mail_plugins notify replication

# The mail processes need to have access to the replication-notify fifo and 
socket.
service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
mode = 0666
  }
  unix_listener replication-notify {
user = vmail
mode = 0666
  }
}

# Enable doveadm replicator commands
service replicator {
  unix_listener replicator-doveadm {
mode = 0666
  }
}

# Create a listener for doveadm-server
service doveadm {
  user = vmail
  inet_listener {
port = 12345
  }
}

# configure how many dsyncs can be run in parallel (10 by default)
replication_max_conns = 10

# tell doveadm client to use this port by default
doveadm_port = 4711

#Both the client and the server also need to have a shared secret
doveadm_password = {SHA512-CRYPT}$6$ro.
# use tcp:hostname as the dsync target
plugin {
  #mail_replica = tcp:server1.domain.ltd # use doveadm_port
  mail_replica = tcp:server1.domain.ltd:12345 # use port 12345 explicitly
}

service config {
  unix_listener config {
user = vmail
  }
}

To test both port   I have open on  my both servers port 12345 and 4711 :

Iptables server1: ACCEPT tcp  --  anywhere anywhere 
tcp dpt:4711
  ACCEPT tcp  --  anywhere anywhere 
tcp dpt:12345

Iptables server2: ACCEPT tcp  --  anywhere anywhere 
tcp dpt:4711
  ACCEPT tcp  --  anywhere anywhere 
tcp dpt:12345


doveadm replicator  status '*'
username
priority fast sync full sync failed
us...@domain.ltd
none 00:01:21  11:25:40  y
us...@domain.ltd
none 07:31:16  11:25:41  -
us...@domain.ltd
none 00:01:21  11:25:40  y
us...@domain.ltd
none 11:25:41  11:25:41  -
us...@domain.ltd
none 02:17:03  11:25:41  -
us...@domain.ltd
none 11:25:40  11:25:40  -
us...@domain.ltd
none 00:00:51  11:25:40  y

When  doing, from server1:   "doveadm sync -u us...@domain.ltd 
remote:server2.domain.ltd"

doveadm(us...@domain.ltd): Error: userdb lookup: 
connect(/var/run/dovecot/auth-userdb) failed: Connection refused
doveadm(us...@domain.ltd): Fatal: /var/run/dovecot/auth-userdb: passdb lookup 
failed (to see if user is proxied, because doveadm_port is set)
dsync-local(us...@domain.ltd): Error: read(server2.domain.ltd) failed: EOF 
(version not received)

Thx for your help.

Re: dsync dovecot / Failed connection refused

2017-01-24 Thread Mike Fröhner

Sorry, you are right, I was wrong. I missed you explicit configure the 
port at $mail_replica.


On 01/24/2017 10:45 AM, Thierry wrote:

Hi Mike,

Is  the value of  the 'doveadm_port' if I am choosing: mail_replica =
tcp:server1.domain.ltd   no ?
I might be wrong too ;)

Thx

Le mardi 24 janvier 2017 à 11:41:28, vous écriviez :


Hello,



I might be wrong, but the port which will be used for the replicator
port is the value of 'doveadm_port' which in your case is 4711.



Mike;



On 01/23/2017 05:58 PM, Thierry wrote:

Dear all,

I am using VMWare and I  have cloned my emails server.
Now I do have two identicals servers, both running the same version of dovecot 
(2.2.13) and imap.
Let's call them: server1.domain.ltd  and server2.domain.ltd.
I would  like to sync both server using dsync.

Dovecot is working well except concerning  the sync.

dsync config server1.domain.ltd

# Enable the replication plugin globally
mail_plugins = $mail_plugins notify replication

# The mail processes need to have access to the replication-notify fifo and 
socket.
service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
mode = 0666
  }
  unix_listener replication-notify {
user = vmail
mode = 0666
  }
}

# Enable doveadm replicator commands
service replicator {
  unix_listener replicator-doveadm {
mode = 0666
  }
}

# Create a listener for doveadm-server
service doveadm {
  user = vmail
  inet_listener {
port = 12345
  }
}

# configure how many dsyncs can be run in parallel (10 by default)
replication_max_conns = 10

# tell doveadm client to use this port by default
doveadm_port = 4711

#Both the client and the server also need to have a shared secret
doveadm_password = {SHA512-CRYPT}$6$rou
# use tcp:hostname as the dsync target
plugin {
  #mail_replica = tcp:server2.domain.ltd # use doveadm_port
  mail_replica = tcp:server2.domain.ltd:12345 # use port 12345 explicitly
}

service config {
  unix_listener config {
user = vmail
  }
}

***

dsync config server2.domain.ltd

# Enable the replication plugin globally
mail_plugins = $mail_plugins notify replication

# The mail processes need to have access to the replication-notify fifo and 
socket.
service aggregator {
  fifo_listener replication-notify-fifo {
user = vmail
mode = 0666
  }
  unix_listener replication-notify {
user = vmail
mode = 0666
  }
}

# Enable doveadm replicator commands
service replicator {
  unix_listener replicator-doveadm {
mode = 0666
  }
}

# Create a listener for doveadm-server
service doveadm {
  user = vmail
  inet_listener {
port = 12345
  }
}

# configure how many dsyncs can be run in parallel (10 by default)
replication_max_conns = 10

# tell doveadm client to use this port by default
doveadm_port = 4711

#Both the client and the server also need to have a shared secret
doveadm_password = {SHA512-CRYPT}$6$ro.
# use tcp:hostname as the dsync target
plugin {
  #mail_replica = tcp:server1.domain.ltd # use doveadm_port
  mail_replica = tcp:server1.domain.ltd:12345 # use port 12345 explicitly
}

service config {
  unix_listener config {
user = vmail
  }
}

To test both port   I have open on  my both servers port 12345 and 4711 :

Iptables server1: ACCEPT tcp  --  anywhere anywhere 
tcp dpt:4711
  ACCEPT tcp  --  anywhere anywhere 
tcp dpt:12345

Iptables server2: ACCEPT tcp  --  anywhere anywhere 
tcp dpt:4711
  ACCEPT tcp  --  anywhere anywhere 
tcp dpt:12345


doveadm replicator  status '*'
username
priority fast sync full sync failed
us...@domain.ltd
none 00:01:21  11:25:40  y
us...@domain.ltd
none 07:31:16  11:25:41  -
us...@domain.ltd
none 00:01:21  11:25:40  y
us...@domain.ltd
none 11:25:41  11:25:41  -
us...@domain.ltd
none 02:17:03  11:25:41  -
us...@domain.ltd
none 11:25:40  11:25:40  -
us...@domain.ltd
none 00:00:51  11:25:40  y

When  doing, from server1:   "doveadm sync -u us...@domain.ltd 
remote:server2.domain.ltd"

doveadm(us...@domain.ltd): Error: userdb lookup: 
connect(/var/run/dovecot/auth-userdb) failed: Connection refused
doveadm(us...@domain.ltd): Fatal: /var/run/dovecot/auth-userdb: passdb lookup 
failed (to see if

Re: dsync dovecot / Failed connection refused

2017-01-26 Thread Mike Fröhner

Your output looks like iptables -L -n. Can you add the -v option to 
check if the rule did handle packages?


On 01/26/2017 05:39 PM, Thierry wrote:

ACCEPT tcp  --  anywhere anywhere tcp dpt:4711

Re: Dovecot dsync 'ssl_client_ca'

2017-02-03 Thread Mike Fröhner


Hello,


On 02/03/2017 08:51 AM, Thierry wrote:

Hello,

Still working with my dsync pb.
I have done a clone (vmware) of my email server.
Today   I   have   two  strictly  identical  emails  servers (server1
(main) and server2 (bck) (except IP, hostname and  mail_replica).

The ssl config on my both server:

ssl_protocols = !SSLv2 !SSLv3
ssl = required
verbose_ssl = no
ssl_key = 

I think it should be ssl_client_ca_file = 





This  config  is  working   for  my   email  client  and my email web
interface ...

Are they on the right order ?

mail_replica = tcps:serv...@domain.ltd and tcps:serv...@domain.ltd

There is trafic on my iptables rules on my both  servers:

60  3600 ACCEPT tcp  --  *  *   0.0.0.0/00.0.0.0/0  
  tcp dpt:4711



My  error message from server1 (main server):

Feb 03 08:38:08 doveadm(us...@domain.ltd): Error: sync: Couldn't initialize SSL 
context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* 
settings)
Feb 03 08:42:35 doveadm(us...@domain.ltd): Error: sync: Couldn't initialize SSL 
context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* 
settings)
Feb 03 08:42:35 doveadm(us...@domain.ltd): Error: sync: Couldn't initialize SSL 
context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* 
settings)
Feb 03 08:42:35 doveadm(us...@domain.ltd): Error: sync: Couldn't initialize SSL 
context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* 
settings)

No logs from server2

Any ideas ?

Thx for your support

Pop3 service stops responding

2015-06-02 Thread Mike Eriksson

Hi!

I have problem with the pop3 service stops responding at random intervals
on my server. We started to notice this problem as we're running icinga to
check the imap & pop3 service.

When icinga reports that the service is down. We try to telnet to the
server on port 110 but it refuses the connection.

I've checked the netstat during this time and it's listens on port 110. My
first thought we were hitting the max connections and similar.

Changed login_max_connections from 128 to 256. Didnt solve the problem.

Started the debug on the dovecot server but could not see anything in the
logs. Also the error log or the syslog dosnt report anything that I can see.

Best thing would of course be to start and upgrade the software and
os(Debian 5) but I'm not comfortable upgrading it at the moment as my
knowledge about dovecot / postfix isn't great.

Do you have any idéas how to move forward?

dovecot -n
# 1.0.15: /etc/dovecot/dovecot.conf
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot-error.log
info_log_path: /var/log/dovecot-info.log
log_timestamp: %Y-%m-%d %H:%M:%S
protocols: pop3 imap imaps pop3s
ssl_cipher_list: ALL:!LOW
disable_plaintext_auth: no
login_dir: /var/run/dovecot//login
login_executable(default): /usr/lib/dovecot/imap-login
login_executable(imap): /usr/lib/dovecot/imap-login
login_executable(pop3): /usr/lib/dovecot/pop3-login
login_max_processes_count: 256
first_valid_uid: 1090
last_valid_uid: 1090
first_valid_gid: 1090
last_valid_gid: 1090
mail_privileged_group: mail
mail_location: maildir:~/Maildir
mail_executable(default): /usr/lib/dovecot/imap
mail_executable(imap): /usr/lib/dovecot/imap
mail_executable(pop3): /usr/lib/dovecot/pop3
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugin_dir(default): /usr/lib/dovecot/modules/imap
mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
auth default:
  username_chars:
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@%
  username_translation: %@
  username_format: %Lu
  passdb:
driver: sql
args: /etc/dovecot/dovecot-sql.conf
  userdb:
driver: passwd
  userdb:
driver: sql
args: /etc/dovecot/dovecot-sql.conf
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix
master:
  path: /var/run/dovecot/auth-master
  mode: 384
  user: vmail
  group: vmail
plugin:
  quota: maildir
  sieve_global_path: /etc/dovecot/sieve_scripts/spam-sort.sieve

login_max_processes_count: 256
login_max_connections: 256
max_mail_processes: 1024

Best Regards
Mike

passwd mismatch

2016-05-18 Thread Mike Ponto

I have been trying to follow the "instructions" at 
"http://blog.iandreev.com/?p=1975#dovecot"; and they seem to be pretty 
good.  everything works until I get to the part were I test the dovecot 
installation and it keeps failing.

I get an AUTH fail error at the "telnet localhost 110" login commands

I am trying to setup 3 domains:
domain1.us
domain2.com
domain3.com
I have 4 users entered in the /etc/dovecot/users file
I followed the instructions for creating an encrypted password but don't 
think it is correct and I don't have the knowledge to say why.  Just 
doesn't feel right.


I admit I am over my head and the learning curve just got exponential - 
any help at all would be really appreciated.



System:
QEMU/KVM vitrual install
Centos 7.01
basic install
4096 G Ram
4 proc
120 G HD

unit is behind an IPCop firewall with port forwarding.
internal IP 192.168.1.155
external IP on request

have username in /etc/dovecot/users as such:
mynameh...@mydomainhere.us:

Turned on debuggin and log file shows:
May 18 16:45:02 auth: Debug: auth client connected (pid=5639)
May 18 16:45:16 auth: Debug: client in: AUTH1PLAIN 
service=pop3secured session=2pP4xSQzzgAB
lip=::1 rip=::1 lport=110rport=33742 $
May 18 16:45:16 auth: Debug: 
passwd-file(mynameh...@mydomainhere.us,::1,<2pP4xSQzzgAB>): 
lookup: user=mynameh...@mydomainhere.us file=/etc/dovecot/users
May 18 16:45:16 auth: Info: 
passwd-file(mynameh...@mydomainhere.us,::1,<2pP4xSQzzgAB>): 
Password mismatch
May 18 16:45:18 auth: Debug: client passdb out: FAIL1 
user=mynamehe...@mydomainhere.us
May 18 16:45:20 pop3-login: Info: Aborted login (auth failed, 1 attempts 
in 4 secs): user=, method=PLAIN, rip=::1, 
lip=::1, secured, session=<2pP4xSQzzgAA$

[Dovecot] mbox originally needed 0 bytes, now needs maxint bytes

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, 
amd64.

I've long been getting the following kind of messages in my logs, on 
random occasions when I access or move mail into mboxes:

Aug 16 00:43:58 myhost dovecot: IMAP(mike): mbox /home/mike/mail/feedback: 
seq=88 uid=91 uid_broken=0 originally needed 0 bytes, now needs 
18446744073709551615 bytes

Whatever I'm trying to do always succeeds, but apparently dovecot is confused 
about something. That number (2^64-1) suggests it has to do with the amd64 
architecture. Did a compile option get overlooked?

Thanks for whatever you can suggest. Let me know if you need more info.

[Dovecot] mbox originally needed 0 bytes, now needs maxint bytes

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, 
amd64.

I've long been getting the following in my logs, seemingly at random (so, only 
sometimes), when I access or move mail into mboxes:

Aug 16 00:43:58 myhost dovecot: IMAP(mike): mbox /home/mike/mail/feedback: 
seq=88 uid=91 uid_broken=0 originally needed 0 bytes, now needs 
18446744073709551615 bytes

Whatever I'm trying to do always succeeds, but apparently dovecot is confused 
about something. That number (2^64-1) suggests it has to do with the amd64 
architecture. Did a compile option get overlooked?

Let me know if there's anything I need to do to get rid of these warnings.

Thanks,
Mike

[Dovecot] signal 11 crash, sometimes, during mbox bz2 decompression

Hello again,

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, 
amd64.

To enable IMAP read-only access to gzip or bzip2 compressed mbox files, I 
added the following to my dovecot.conf, in the protocol imap { ... } section: 
mail_plugins = zlib

My compressed mbox files are all .bz2 files in an 'old' subdirectory of my 
main mail directory. I am trying to access them with Thunderbird. I 
'subscribed' to them just fine, and at first I thought it was working, but I 
just got lucky on the first couple I accessed. Dovecot actually fails to 
decompress them about 90% of the time, seemingly at random; the same box will 
not work a bunch of times, then work once, then not work again and again. When 
it works, sometimes only some of the messages get transmitted.

Most of the failures are accompanied by this pair of messages in my log:

Aug 16 00:25:33 myhost dovecot: dovecot: child 943 (imap) killed with signal 11 
(core not dumped - set mail_drop_priv_before_exec=yes)
Aug 16 00:25:33 myhost kernel: pid 943 (imap), uid 1001: exited on signal 11

Some of the failures have only the "exited on signal 11" message.

The very first failure had this:

Aug 16 00:22:47 myhost dovecot: IMAP(mike): Next message unexpectedly lost from 
mbox file (read-only mbox stream) at 2761 (cached)
Aug 16 00:22:47 myhost dovecot: IMAP(mike): read(mail, uid=2) failed: Invalid 
argument


Is this a problem with dovecot? Let me know if/how I can help, or what other 
info you need.


Thanks,
Mike

Re: [Dovecot] mbox originally needed 0 bytes, now needs maxint bytes

Sorry for the duplicate post. I lost my network connection right as I was 
sending the first one.

Re: [Dovecot] signal 11 crash, sometimes, during mbox bz2 decompression

2011-09-12 Thread Mike Brown


On 8/23/2011 11:47 AM, Timo Sirainen wrote:

On Tue, 2011-08-16 at 05:00 -0600, Mike Brown wrote:


I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE,
amd64.

..


Thanks for the reply. Since you recommended updating to dovecot2, I'm 
now testing dovecot 2.0.14 from the ports collection on a different 
machine. Hopefully I got the configuration right.


# dovecot -n
# 2.0.14: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-RELEASE-p2 i386
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_plugins = " zlib"
passdb {
  args = %s
  driver = pam
}
plugin {
  zlib_save = bz2
  zlib_save_level = 9
}
protocols = imap
ssl_cert = On this system, I have the same setup with bz2-compressed mbox files. 
They're still inaccessible from Thunderbird, but dovecot isn't crashing 
with signal 11 anymore. Instead, the maillog says this for every 
compressed box it tries to check:


Sep 12 02:37:14 chilled dovecot: imap(mike): Error: 
read(/home/mike/mail/old/sent-1999-07.bz2) failed: Invalid argument (uid=2)
Sep 12 02:37:14 chilled dovecot: imap(mike): Disconnected: Internal 
error occurred. Refer to server log for more information. [2011-09-12 
02:37:14] bytes=5492/2664368
Sep 12 02:37:14 chilled dovecot: imap(mike): Error: Next message 
unexpectedly lost from mbox file /home/mike/mail/old/sent-1999-07.bz2 at 
536 (cached)


Did I misconfigure something?

[Dovecot] two little fixes for 2.0.14

2011-09-12 Thread Mike Abbott

--- a/dovecot/src/lib-index/mail-index-view.c
+++ b/dovecot/src/lib-index/mail-index-view.c
@@ -9,7 +9,7 @@
 void mail_index_view_clone(struct mail_index_view *dest,
   const struct mail_index_view *src)
 {
-   memset(dest, 0, sizeof(dest));
+   memset(dest, 0, sizeof(*dest));
dest->refcount = 1;
dest->v = src->v;
dest->index = src->index;


--- a/dovecot/src/lib-storage/mail-storage-service.c
+++ b/dovecot/src/lib-storage/mail-storage-service.c
@@ -870,7 +870,7 @@
}
 
user = p_new(user_pool, struct mail_storage_service_user, 1);
-   memset(user_r, 0, sizeof(user_r));
+   memset(user_r, 0, sizeof(*user_r));
user->pool = user_pool;
user->input = *input;
user->input.userdb_fields = NULL;

Re: [Dovecot] signal 11 crash, sometimes, during mbox bz2 decompression

2011-09-12 Thread Mike Brown


On 9/12/2011 5:28 AM, Timo Sirainen wrote:
Oh, wonder why no one else has complained about that. Fixed: 
http://hg.dovecot.org/dovecot-2.0/rev/a930318a74a1 

I tested this patch, and it's working like a charm. Thanks!

[Dovecot] Shredding instead of deleting

2011-09-14 Thread Mike Cardwell

Hi,

I have a wishlist item. Is there an appropriate place for me to post it?
Basically, I would like to know that my email isn't recoverable from the
local disk on the mail server after I delete it. So instead of just
deleting the file from my Maildir, I'd like the option to exist for
Dovecot to shred it.. Ie, overwrite the file with random data and/or
null bytes before deletion. In the same way that GNU shred behaves:

https://www.gnu.org/software/coreutils/manual/html_node/shred-invocation.html

-- 
Mike Cardwell https://grepular.com/  https://twitter.com/mickeyc
Professional  http://cardwellit.com/ http://linkedin.com/in/mikecardwell
PGP.mit.edu   0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F



signature.asc
Description: OpenPGP digital signature

Re: [Dovecot] outlook 2007 very slow.

2011-09-20 Thread Mike Cardwell

On 20/09/11 11:46, Charles Marcus wrote:

>>> and is even better in 2010
> 
>> Do they support ACL in 2010? They don't in 2007, which is really
>> frustrating. What is better about 2010 IMAP support compared to 2007?
>> I'm genuinely interested to know...
> 
> What do you mean by 'ACL support'? Do you mean the ability to 
> create/edit them on shared folders?

Yes. Support for the IMAP ACL extension.

> If so, then no, not natively, I 
> don't think, but I didn't do any intensive testing, all I can tell you 
> is it is much more responsive, especially on larger folders.

This is a real shame. IMAP can do so much more than Exchange's IMAP
implementation allows.

-- 
Mike Cardwell https://grepular.com/  https://twitter.com/mickeyc
Professional  http://cardwellit.com/ http://linkedin.com/in/mikecardwell
PGP.mit.edu   0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F



signature.asc
Description: OpenPGP digital signature

Re: [Dovecot] 64.31.19.48 attempt to break into my computer

2011-09-22 Thread Mike Cardwell

On 22/09/11 15:08, Charles Marcus wrote:

> The only attack I haven't figured out how to eliminate is the
> social/phishing attack, where $DumbUser gives out their username
> password voluntarily... although I have been considering faking a
> phishing attack on my own users, and flagging the ones who fall for it
> for training.

The University I work at was suffering from this a *lot*. Phishers kept
contacting our users pretending to be from our IT helpdesk asking users
to reply with their login details so that their mailbox could be
refreshed or so their quota could be fixed and other such things.

So I developed an application that sits on our outgoing mail routers
looking for login credentials inside emails. If it finds any, it
blackholes the email and sends an autoresponse to the sender telling
them to never ever send login details via email under any circumstances.
It Cc's me in too, and it catches people emailing their logins around on
a *daily* basis.

Our usernames follow a very strict format, and we have a pretty strict
password policy so what my program does is pull out a list of all the
*possible* usernames and passwords and then attempts to authenticate
against our AD using them.

I built it into a framework so other people can use it:

http://kochi.lboro.ac.uk/kochi1.html

You need to know how to write Perl though in order to use it. It's not
plug and play.

We also added ratelimiting to our outgoing mail, and a system which
alerts us whenever anyone hits the limit. If it takes a phisher 2000
spams to get access to one account, but that one account only allows the
phisher to send 1000 spams, then it completely destroys the point of
what they're doing.

-- 
Mike Cardwell https://grepular.com/  https://twitter.com/mickeyc
Professional  http://cardwellit.com/ http://linkedin.com/in/mikecardwell
PGP.mit.edu   0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F

signature.asc
Description: OpenPGP digital signature

Re: [Dovecot] 64.31.19.48 attempt to break into my computer

2011-09-22 Thread Mike Cardwell

On 22/09/11 15:21, Ralf Hildebrandt wrote:

>> The University I work at was suffering from this a *lot*. Phishers kept
>> contacting our users pretending to be from our IT helpdesk asking users
>> to reply with their login details so that their mailbox could be
>> refreshed or so their quota could be fixed and other such things.
> 
> Same here.
> 
>> So I developed an application that sits on our outgoing mail routers
>> looking for login credentials inside emails. If it finds any, it
>> blackholes the email and sends an autoresponse to the sender telling
>> them to never ever send login details via email under any circumstances.
>> It Cc's me in too, and it catches people emailing their logins around on
>> a *daily* basis.
> 
> clamav is supposed to be capable of that functionality
>
>> Our usernames follow a very strict format, and we have a pretty strict
>> password policy so what my program does is pull out a list of all the
>> *possible* usernames and passwords and then attempts to authenticate
>> against our AD using them.
> 
> Ah!
> That's a nice idea.

Perhaps, if you have a list of the plain text passwords in advance you
could use ClamAV. In our case, we don't as we're using an AD. I actually
copied the ClamAV tcp and local interface API so that any MTA which can
plug in to ClamAV is also able to plug into Kochi. That's one of the
things the framework provides.

-- 
Mike Cardwell https://grepular.com/  https://twitter.com/mickeyc
Professional  http://cardwellit.com/ http://linkedin.com/in/mikecardwell
PGP.mit.edu   0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F



signature.asc
Description: OpenPGP digital signature

[Dovecot] another sizeof tweak

2011-11-08 Thread Mike Abbott

Line 776 of dovecot-2.0.15/src/lib-storage/index/maildir/maildir-sync-index.c 
reads:
memcmp(old_rec, &new_rec, sizeof(old_rec)) != 0) {
Should that be sizeof(*old_rec)?

[Dovecot] dovecot 2.1.rc1 and folders with umlauts

2011-12-07 Thread Mike Constabel

Hi,

if I try to crate a folder in Thunderbird 8 which contains 
umlauts this happens:

- Create folder "Tür"
- Thunderbird show T&APw-r in folder list

In log:

Dec 07 17:45:39 imap(te...@in-preetz.de): Debug: Namespace : 
/mailspool1/in-preetz.de/test1/mdbox/mailboxes/T&APw-r doesn't exist yet, using 
default permissions
Dec 07 17:45:39 imap(te...@in-preetz.de): Debug: Namespace : Using permissions 
from /mailspool1/in-preetz.de/test1/mdbox: mode=0700 gid=-1

# ll /mailspool1/in-preetz.de/test1/mdbox/mailboxes/
insgesamt 32K
drwx-- 8 vmail vmail 4,0K  7. Dez 17:45 .
drwx-- 4 vmail vmail 4,0K  7. Dez 17:45 ..
drwx-- 3 vmail vmail 4,0K 29. Nov 11:11 Drafts
drwx-- 3 vmail vmail 4,0K 29. Nov 11:04 INBOX
drwx-- 3 vmail vmail 4,0K 29. Nov 11:11 Junk
drwx-- 3 vmail vmail 4,0K 29. Nov 11:11 Sent
drwx-- 3 vmail vmail 4,0K  7. Dez 17:45 T&APw-r
drwx-- 4 vmail vmail 4,0K  7. Dez 17:44 Trash

If I click in TB on the folder, TB gives an empty message, the 
log shows:

Dec 07 17:42:53 imap(te...@in-preetz.de): Debug: Effective uid=1000, gid=1000, 
home=/mailspool1/in-preetz.de/test1
Dec 07 17:42:53 imap(te...@in-preetz.de): Debug: quota: No quota setting - 
plugin disabled
Dec 07 17:42:53 imap(te...@in-preetz.de): Debug: Namespace inbox: type=private, 
prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes 
location=mdbox:~/mdbox
Dec 07 17:42:53 imap(te...@in-preetz.de): Debug: fs: 
root=/mailspool1/in-preetz.de/test1/mdbox, index=, control=, inbox=, alt=
Dec 07 17:42:53 imap(te...@in-preetz.de): Debug: Namespace : Using permissions 
from /mailspool1/in-preetz.de/test1/mdbox: mode=0700 gid=-1
Dec 07 17:43:02 imap(te...@in-preetz.de): Debug: Namespace : 
/mailspool1/in-preetz.de/test1/mdbox/mailboxes/&ANY-de doesn't exist yet, using 
default permissions
Dec 07 17:43:02 imap(te...@in-preetz.de): Debug: Namespace : Using permissions 
from /mailspool1/in-preetz.de/test1/mdbox: mode=0700 gid=-1
Dec 07 17:44:19 imap(te...@in-preetz.de): Debug: Namespace : 
/mailspool1/in-preetz.de/test1/mdbox/mailboxes/&-ANY-de doesn't exist yet, 
using default permissions
Dec 07 17:44:19 imap(te...@in-preetz.de): Debug: Namespace : Using permissions 
from /mailspool1/in-preetz.de/test1/mdbox: mode=0700 gid=-1
Dec 07 17:44:19 imap(te...@in-preetz.de): Debug: Namespace : 
/mailspool1/in-preetz.de/test1/mdbox/mailboxes/Trash/&-ANY-de doesn't exist 
yet, using default permissions
Dec 07 17:44:24 imap(te...@in-preetz.de): Debug: Namespace : 
/mailspool1/in-preetz.de/test1/mdbox/mailboxes/Trash/T&APw-r doesn't exist yet, 
using default permissions
Dec 07 17:45:39 imap(te...@in-preetz.de): Debug: Namespace : 
/mailspool1/in-preetz.de/test1/mdbox/mailboxes/T&APw-r doesn't exist yet, using 
default permissions
Dec 07 17:45:39 imap(te...@in-preetz.de): Debug: Namespace : Using permissions 
from /mailspool1/in-preetz.de/test1/mdbox: mode=0700 gid=-1


On another server with

# 2.0.13 (537d4b6d9a7a): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-686 i686 Debian 6.0.2 

an an server with

# 1.2.16: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 5.0.9 

umlauts are working.

Is there an problem with my config or with the rc1?


thanks,
Mike


dovecot -n for not working 2.1.rc1:

# 2.1.rc1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 
auth_cache_size = 1 M
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login cram-md5
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot/dovecot-debug.log
default_client_limit = 2600
disable_plaintext_auth = no
hostname = mx4.constabel-it.de
info_log_path = /var/log/dovecot/dovecot-info.log
log_path = /var/log/dovecot/dovecot.log
mail_debug = yes
mail_location = mdbox:~/mdbox
mail_plugins = quota notify mail_log
mail_privileged_group = mail
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 ihave
namespace inbox {
  inbox = yes
  location = 
  prefix = 
  separator = /
  type = private
}
passdb {
  args = scheme=PLAIN username_format=%u /etc/imap.userdb
  driver = passwd-file
}
plugin {
  autocreate = Trash
  autocreate2 = Junk
  autocreate3 = Sent
  autocreate4 = Drafts
  autosubscribe = Trash
  autosubscribe2 = Junk
  autosubscribe3 = Sent
  autosubscribe4 = Drafts
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
postmaster_address = postmaster@localhost
protocols = " imap lmtp sieve pop3"
service auth {
  inet_listener {
address = 192.168.10.117
port = 12345
  }
}
service imap-login {
  inet_listener imap {
address = 192.168.10.117
port = 143
  }
  inet_listener imaps {
address = 192.168.10.117
port = 993
ssl = yes
  }
}
service lmtp {
  inet_listener

Re: [Dovecot] dovecot 2.1.rc1 and folders with umlauts

2011-12-08 Thread Mike Constabel

Hi,

Timo Sirainen schrieb am Thursday, den 08. December 2011:

> On Wed, 2011-12-07 at 18:05 +0100, Mike Constabel wrote:
> 
> > if I try to crate a folder in Thunderbird 8 which contains 
> > umlauts this happens:
> > 
> > - Create folder "Tür"
> > - Thunderbird show T&APw-r in folder list
> 
> I can't reproduce. Is it possible this is a TB bug? Try talking IMAP
> protocol directly:
> 
> /usr/local/libexec/dovecot/imap -u user@domain
> a list "" T*
> 
> If it lists:
> 
> * LIST (\HasNoChildren) "." "T&APw-r"
> 
> Then Dovecot is working correctly.

I get:

# /usr/lib/dovecot/imap -u te...@in-preetz.de
Debug: Loading modules from directory: /usr/lib/dovecot/modules
Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so
Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so
Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so
Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so
Debug: auth input: te...@in-preetz.de uid=1000 gid=1000 
home=/mailspool1/in-preetz.de/test1 quota_rule=*:storage=500M
Debug: Added userdb setting: plugin/quota_rule=*:storage=500M
Debug: Effective uid=1000, gid=1000, home=/mailspool1/in-preetz.de/test1
Debug: quota: No quota setting - plugin disabled
Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, 
list=yes, subscriptions=yes location=mdbox:~/mdbox
Debug: fs: root=/mailspool1/in-preetz.de/test1/mdbox, index=, control=, inbox=, 
alt=
Debug: Namespace : Using permissions from /mailspool1/in-preetz.de/test1/mdbox: 
mode=0700 gid=-1
* PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE 
SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN 
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT 
SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS FUZZY SPECIAL-USE QUOTA] Logged in 
as te...@in-preetz.de
a list "" T*
* LIST (\HasNoChildren) "/" "T&-APw-r"
* LIST (\HasChildren) "/" "Trash"
* LIST (\HasNoChildren) "/" "Trash/T&-APw-r"
a OK List completed.

As you see there is a second "-" in the name:

"T&APw-r" != "T&-APw-r"

With my old server:

# telnet 192.168.10.102 143
Trying 192.168.10.102...
Connected to 192.168.10.102.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS 
AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5] Dovecot ready.
A login aaa bbb
A OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT 
SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN 
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT 
SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk QUOTA] Logged in
a list "" T*
* LIST (\HasNoChildren) "/" "Trash"
* LIST (\HasNoChildren) "/" "Test-1"
* LIST (\HasNoChildren) "/" "T&APw-r"
a OK List completed.

Mike

Re: [Dovecot] dovecot 2.1.rc1 and folders with umlauts

2011-12-10 Thread Mike Constabel

Hi,

Timo Sirainen schrieb am Saturday, den 10. December 2011:

> On Thu, 2011-12-08 at 11:19 +0200, Timo Sirainen wrote:
> > On Thu, 2011-12-08 at 09:55 +0100, Mike Constabel wrote:
> > 
> > > As you see there is a second "-" in the name:
> > > 
> > > "T&APw-r" != "T&-APw-r"
> > 
> > Oh, right, it's broken in the "fs" layout. With "maildir++" layout it
> > works. And looks like this isn't going to be an easy fix. The fs layout
> > listing code is horrible.. Maybe I'll just try rewriting it.
> 
> OK, this should do it, hopefully without breaking anything:
> http://hg.dovecot.org/dovecot-2.1/rev/ab696ead12cc
> 

This works for me with a litte problem.

If I create in TB folder like "moe" (without special chars) the 
folder will be created, subscribed and TB shows the folder 
instantly.

But if I create a folder like "mö" (with special chars) the 
folder will be created, subscribed and *TB doesn't show the 
folder*. I must unsubscribe and subscribe it in TB to show it in 
folder pane.

Mike

Re: [Dovecot] dovecot 2.1.rc1 and folders with umlauts

On Mon, 12 Dec 2011, Timo Sirainen wrote:

> On Sat, 2011-12-10 at 15:10 +0100, Mike Constabel wrote:
> > > OK, this should do it, hopefully without breaking anything:
> > > http://hg.dovecot.org/dovecot-2.1/rev/ab696ead12cc
> > > 
> > 
> > This works for me with a litte problem.
> > 
> > 
> > If I create in TB folder like "moe" (without special chars) the 
> > folder will be created, subscribed and TB shows the folder 
> > instantly.
> > 
> > But if I create a folder like "mö" (with special chars) the 
> > folder will be created, subscribed and *TB doesn't show the 
> > folder*. I must unsubscribe and subscribe it in TB to show it in 
> > folder pane.
> 
> http://hg.dovecot.org/dovecot-2.1/rev/b9fcac239aed should fix it.
> 

Yes, it works. Thanks.


Mike

[Dovecot] dovecot 2.1.rc1: sieve and folders with umlauts

Hi,

now the umlauts problem with sieve:

# cat /mailspool1/in-preetz.de/test1/.dovecot.sieve
## Generated by Roundcube Webmail SieveRules Plugin ##
require ["fileinto"];

# rule:[Test]
if anyof (header :contains "Subject" "test")
{
fileinto "m&APY-";
}



Error: DBBjDsXL5U7mIAAA/TNBsA: sieve: execution of script 
/mailspool1/in-preetz.de/test1/.dovecot.sieve failed, but implicit keep was 
successful (user logfile /mailspool1/in-preetz.de/test1/.dovecot.sieve.log may 
reveal additional details)


# cat /mailspool1/in-preetz.de/test1/.dovecot.sieve.log
sieve: info: started log at Dec 12 10:40:04.
error: msgid=<20111212094004.db86918...@mx4.constabel-it.de>: failed to store 
into mailbox 'm&APY-': Mailbox doesn't exist: m&-APY-.


Here the same:

'm&APY-' != "m&-APY-"



Mike

Re: [Dovecot] dovecot 2.1.rc1: sieve and folders with umlauts

Hello,

On 2011-12-12 at 10:58 CET Timo Sirainen wrote:

> On 12.12.2011, at 11.46, Mike Constabel wrote:
> 
> > now the umlauts problem with sieve:
> ..
> > ## Generated by Roundcube Webmail SieveRules Plugin ##
> 
> Roundcube bug/"feature".
> 
> >fileinto "m&APY-";
> 
> Sieve uses UTF-8 mailbox names. The reason why Roundcube doesn't use them, is 
> because some old Cyrus Sieve versions didn't use UTF-8.

Ok, good to know. I found the setting in the roundcube sieverules 
plugin. After setting this to UTF-8 it works.

Thanks for the hint.

Mike

Re: [Dovecot] dovecot 2.1.rc1: sieve and folders with umlauts

Hello Stephan,

On 2011-12-12 at 11:00 CET Stephan Bosch wrote:

> Op 12/12/2011 10:46 AM, Mike Constabel schreef:
> >Hi,
> >
> >now the umlauts problem with sieve:
> >
> ># cat /mailspool1/in-preetz.de/test1/.dovecot.sieve
> >## Generated by Roundcube Webmail SieveRules Plugin ##
> >require ["fileinto"];
> >
> ># rule:[Test]
> >if anyof (header :contains "Subject" "test")
> >{
> > fileinto "m&APY-";
> >}
> 
> And here it is actually correct. Sieve fileinto expects the argument
> to be in utf8 and you are passing the IMAP mutf7.
> 
> Use
> 
> fileinto "mö";
> 
> instead.

Thanks for the hint, now it works. :)

Mike

[Dovecot] v2.1.rc1 managesieve TLS