search for: telsch

...wrote: > I have to correct myself. I tested with sdbox now too, and it seems that > using > > mail_location=sdbox:~/Mail > > produces the expected behaviour. mdbox uses same code as sdbox for this, > so it should work fine. > > Aki > > > On 15.05.2018 13:01, telsch wrote: >> I use mdbox not maildir: >> >> ????mail_location = mdbox:/var/spool/mail/%u >> >> On 15.05.2018 11:53, Aki Tuomi wrote: >>> Do you have >>> >>> mail_location=maildir:~/mail >>> >>> or >>> >>> mai...

...ed, but i didn't found documentation for mail_home= Thanks On 15.05.2018 20:10, Aki Tuomi wrote: > > Well, that's not what I asked you to try... > > try > > mail_home=/var/spool/mail/%u > mail_location=mdbox:~/ > > Aki > >> On 15 May 2018 at 20:03 telsch <telsch at gmx.de> wrote: >> >> >> With this settings I don't get the expectet result, still get wrong >> permissions on new mailboxes. Aki did you also try with %u ? >> >> > In /etc/dovecot/conf.d/10-mail.conf follow options are set: >> &g...

....05.2018 11:53, Aki Tuomi wrote: > Do you have > > mail_location=maildir:~/mail > > or > > mail_location = maildir:/path/to/whatever/%u > > I tested with latest 2.2 that if I use /path/to, I get correct permissions. > > Aki > > > On 15.05.2018 12:43, telsch wrote: >> I would expect same permissions as for root mail directory 02770: >> ????drwxrws--- 5 newuser mail 4096 Apr 23 19:31 /var/spool/mail/newuser/ >> >> Using Dovecot 2.2.34 >> >> On 14.05.2018 08:37, Aki Tuomi wrote: >>> >>> >>>...

As mentioned on earlier email, are you sure you are connecting to port 4190 and not 143 for ManageSieve? Aki > On 06/11/2019 17:48 telsch via dovecot <dovecot at dovecot.org> wrote: > > > I need a more detailed hint. Dovecot proxy IMAP is running fine, but how > to add to the same proxy managesieve support? > > I thougt it's activated in the proxy: > protocols = imap sieve > > In the passdb...

...turned from passdb as they are needed pre-auth. Sami > On 6 Nov 2019, at 16.51, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > > You are hardcoding the port. I'm pretty sure your managesieve is not listening on 143 =) > > Aki > >> On 06/11/2019 16:46 telsch via dovecot <dovecot at dovecot.org> wrote: >> >> >> If i change it to: >> >> passdb { >> args = /etc/dovecot-proxy/dovecot-ldap-passdb.conf.ext >> default_fields = proxy=y host=server.intra.lan port=143 starttls=yes >> master=proxy pass=...

Well, that's not what I asked you to try... try mail_home=/var/spool/mail/%u mail_location=mdbox:~/ Aki > On 15 May 2018 at 20:03 telsch <telsch at gmx.de> wrote: > > > With this settings I don't get the expectet result, still get wrong > permissions on new mailboxes. Aki did you also try with %u ? > > > In /etc/dovecot/conf.d/10-mail.conf follow options are set: > > mail_gid = mail...

...default_fields = proxy=y host=server.intra.lan port=143 starttls=yes master=proxy pass=#hidden_use-P_to_show# driver = ldap } I still got the same error for mangesieve. IMAP login works with both SSL/STARTTLS. On 11/6/19 3:19 PM, Aki Tuomi via dovecot wrote: > >> On 06/11/2019 16:15 telsch via dovecot <dovecot at dovecot.org> wrote: >> >> >> Hello list, >> >> i'm running an internal dovecot instance with working managesieve. But >> on my external dovecot-proxy instance i got an internal error. Nothing >> logs on internal dovecot. &g...

I would expect same permissions as for root mail directory 02770: drwxrws--- 5 newuser mail 4096 Apr 23 19:31 /var/spool/mail/newuser/ Using Dovecot 2.2.34 On 14.05.2018 08:37, Aki Tuomi wrote: > > > On 09.05.2018 12:52, telsch wrote: >> Hello, >> >> the wiki page describe that permission should copied from root mail >> directory >> ????https://wiki2.dovecot.org/SharedMailboxes/Permissions >> >> The permissions for the root mail directory are set to 2770: >> ????drwxrws---...

I have to correct myself. I tested with sdbox now too, and it seems that using mail_location=sdbox:~/Mail produces the expected behaviour. mdbox uses same code as sdbox for this, so it should work fine. Aki On 15.05.2018 13:01, telsch wrote: > I use mdbox not maildir: > > ????mail_location = mdbox:/var/spool/mail/%u > > On 15.05.2018 11:53, Aki Tuomi wrote: >> Do you have >> >> mail_location=maildir:~/mail >> >> or >> >> mail_location = maildir:/path/to/whatever/%u >&gt...

...r=proxy pass=#hidden_use-P_to_show# and enable STARTTLS for IMAP on the backend. Thanks! On 11/6/19 5:05 PM, Aki Tuomi via dovecot wrote: > As mentioned on earlier email, are you sure you are connecting to port 4190 and not 143 for ManageSieve? > > Aki > >> On 06/11/2019 17:48 telsch via dovecot <dovecot at dovecot.org> wrote: >> >> >> I need a more detailed hint. Dovecot proxy IMAP is running fine, but how >> to add to the same proxy managesieve support? >> >> I thougt it's activated in the proxy: >> protocols = imap sieve &...

Hello, the wiki page describe that permission should copied from root mail directory https://wiki2.dovecot.org/SharedMailboxes/Permissions The permissions for the root mail directory are set to 2770: drwxrws--- 36 root mail 4096 Apr 15 02:30 /var/spool/mail/ But newly created mailboxes get following permissions: drwx--S--- 5 newuser mail 4096 Apr 23 19:31 /var/spool/mail/newuser/ In

Do you have mail_location=maildir:~/mail or mail_location = maildir:/path/to/whatever/%u I tested with latest 2.2 that if I use /path/to, I get correct permissions. Aki On 15.05.2018 12:43, telsch wrote: > I would expect same permissions as for root mail directory 02770: > ????drwxrws--- 5 newuser mail 4096 Apr 23 19:31 /var/spool/mail/newuser/ > > Using Dovecot 2.2.34 > > On 14.05.2018 08:37, Aki Tuomi wrote: >> >> >> On 09.05.2018 12:52, telsch wrote: &g...

> On 07/08/2019 14:28 telsch <telsch at gmx.de> wrote: > > > with v2.2.34 i can use: > > ssl_ca = </etc/ssl/ca-bundle.pem > ssl_cert = </etc/ssl-imap.pem > > after upgrade to v2.3.X it doesn't work like before. > > it's working if i manual cat ca-bundle.pem and ssl-imap.p...

You are hardcoding the port. I'm pretty sure your managesieve is not listening on 143 =) Aki > On 06/11/2019 16:46 telsch via dovecot <dovecot at dovecot.org> wrote: > > > If i change it to: > > passdb { > args = /etc/dovecot-proxy/dovecot-ldap-passdb.conf.ext > default_fields = proxy=y host=server.intra.lan port=143 starttls=yes > master=proxy pass=#hidden_use-P_to_show# >...

...auth. > > Sami > > >> On 6 Nov 2019, at 16.51, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: >> >> You are hardcoding the port. I'm pretty sure your managesieve is not listening on 143 =) >> >> Aki >> >>> On 06/11/2019 16:46 telsch via dovecot <dovecot at dovecot.org> wrote: >>> >>> >>> If i change it to: >>> >>> passdb { >>> args = /etc/dovecot-proxy/dovecot-ldap-passdb.conf.ext >>> default_fields = proxy=y host=server.intra.lan port=143 starttls=yes...

Hello list, i'm running an internal dovecot instance with working managesieve. But on my external dovecot-proxy instance i got an internal error. Nothing logs on internal dovecot. Nov 06 14:55:12 managesieve-login: Error: proxy: Remote sent invalid response: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH=GSSAPI] Dovecot (Ubuntu)

Any idea what?pid 7584 is? Aki On 2.9.2019 14.08, telsch via dovecot wrote: > Hello, > > today i got reappearing mails again, but not from purging. In the logs i > only found this. I've got massive problems by many users because > reappearing mails. If you need more information, i could provide. > > > Sep 02 12:58:43 doveadm:...

On 09.05.2018 12:52, telsch wrote: > Hello, > > the wiki page describe that permission should copied from root mail > directory > ????https://wiki2.dovecot.org/SharedMailboxes/Permissions > > The permissions for the root mail directory are set to 2770: > ????drwxrws--- 36 root mail 4096 Apr 15 02:30 /v...

On Tue, 6 Aug 2019, telsch wrote: > if i cat ssl_ca and ssl_cert into one file and only use ssl_cert it's working with 2.3.X > ssl_ca = </etc/ssl/ca-bundle.pem ssl_cert = </etc/ssl-imap.pem In the words of Montoya, "I do not think it means what you think it means", referring to "ssl_ca"....