similar to: Namespace question

Hello, I have a question regarding the password field of the passwd-file [1]. According to the wiki, the password field assumes a {SCHEME} of CRYPT when the {SCHEME} is not prefixed to this field. So, a passwd-file like: user:password: . . . ? is equivalent to: user:{CRYPT}password: . . . Does that mean an example passwd-file with NEITHER {SCHEME} or password, like: user at

* Thore B?decker <me at foxxx0.de>: > You might need to quote that last argument, otherwise it can get > interpreted by the shell as globbing, which obviously is not what you > want. > > I've been using wildcard arguments enclosed within '' and "" for > various doveadm commands without issues so far. Right. I had thought so too (and forgot to mention

with passdb ldap i guess. ---Aki TuomiDovecot oy -------- Original message --------From: Mark Foley <mfoley at ohprs.org> Date: 03/12/2017 21:18 (GMT+02:00) To: dovecot at dovecot.org Subject: Re: Howto authenticate smartPhone via Active Directory Yes, you are right. This link: https://www.redips.net/linux/android-email-postfix-auth/#section2 shows: passdb pam { } used for

Sorry, I have checked before I wrote first post. Based on docs - the path should be in /etc/dovecot/dovecot.conf or /etc/dovecot/conf.d/10-mail.conf (I have Ubuntu 16.04 LTS). I have some familiar lines in 10-mail.conf: #mail_attachment_dir = #mail_attachment_min_size = 128k #mail_attachment_fs = sis posix #mail_attachment_hash = %{sha1} but all these lines are commented out. So - in theory -

Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and having the same error. We have the mail stores in an NFS filer. Regards > On 19.01.2018 11:55, S?ren Skou wrote: >> Hiya all, >> >> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on >> my testbed. The issue is that from what I can see, mail_fsync

Sure: https://www.reub.net/files/dovecot/lightning-dovecot.conf https://www.reub.net/files/dovecot/thunderstorm-dovecot.conf Updated nightly. Reuben On 1/09/2018 12:26 am, Aki Tuomi wrote: > Can you provide doveconf -n? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot at reub.net> >

well i posted the doveconf... # Pigeonhole version 0.4.21 (92477967)

Hi, I'm using dovecot 2.3.2.1 on Xenial from upstream packages on two Dovecot servers connected with dsync over TCP. E-mails which are deleted via POP3 protocol are not correctly deleted on second server via dsync. Jul 25 09:29:19 mda11 dovecot: pop3(jakub@***)<7587><8xaJ1c1x9uEqAB7QADwAAAAAAAAAAL7v>: expunge: box=INBOX, msgid=<6a75db5d84ff257216a4340d7c0405b2 at

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 <1mikemakuch at gmail.com> > Date: 10/08/2018 18:46 (GMT+02:00) > To:

I think this might be caused by glibc 2.28. I saw a similar error with the "doveadm purge" command after upgrading my system to that version. Michael Marley On 2018-08-31 13:10, Aki Tuomi wrote: > I'll see if this is reproducible > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot at

Here's the configuration: https://pastebin.com/ufyQkaBX On Monday, February 19, 2018 7:15:31 PM PST @lbutlr wrote: > On 2018-02-19 (14:08 MST), jordan.h at startmail.com wrote: > > I'm using SSL for dovecot, and dovecot kindly warned me on startup that I > > > needed the ssl_dh parameter, which I specified: > doveconf -n -------------- next part -------------- A

> On Jul 29, 2018, at 6:02 PM, Alexander Dalloz <ad+lists at uni-x.org> wrote: > > Am 29.07.2018 um 21:02 schrieb J Doe: >> Hello, >> I have a question regarding SSL/TLS settings for Dovecot version 2.2.22. >> In: 10-ssl.conf there are two parameters: >> ssl_protocols >> ssl_cipher_list >> ssl_protocols is commented with ?SSL protocol to

FreeBSD 11.1 / amd64 dovecot --version 2.3.2 (582970113) Pigeonhole version 0.5.2 (7704de5e) I have run 'sieve-test" many times to check out changes in my "sieve" scripts. This morning, it suddenly started issuing this error message: sieve-test(root): Fatal: Couldn't drop privileges: User is missing UID (see mail_uid setting) I am not sure what is wrong or how to correct

here is our config: (doveconf -n) # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.6.11-gentoo x86_64 Gentoo Base System release 2.2 auth_cache_size = 10 M auth_mechanisms = plain login default_client_limit = 1024 default_process_limit = 256 hostname = HOSTNAME imap_client_workarounds = delay-newmail tb-extra-mailbox-sep info_log_path = /var/log/dovecot.log listen = * mail_location =

Or you can implement a policy server yourself. :)The protocol is not complicated, json over http. See?https://wiki.dovecot.org/Auth/Policy ---Aki TuomiDovecot oy -------- Original message --------From: Aki Tuomi <aki.tuomi at dovecot.fi> Date: 21/05/2018 19:13 (GMT+02:00) To: Marc Perkel <marc at perkel.com>, dovecot at dovecot.org Subject: Re: Dovecot blacklist?

No. Neither of those are installed on either system. Reuben On 1/09/2018 12:09 am, Aki Tuomi wrote: > Could apparmor or selinux be causing this! > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot at reub.net> > Date: 31/08/2018 16:50 (GMT+02:00) > To: Dovecot Mailing List <dovecot

This sounds more like misconfiguration to me. Can you provide doveconf -n and full output of namei -vl /full/path/to/mailbox ---Aki TuomiDovecot oy -------- Original message --------From: Yves Goergen <nospam.list at unclassified.de> Date: 19/05/2018 18:51 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: Cannot delete folder The issue still exists. Can

ah well, but i'm not using sql at all. here's doveconf -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.4 auth_cache_negative_ttl = 0 auth_mechanisms = plain login hostname = rhyno.tech mail_debug = yes mail_location = maildir:~/mail namespace inbox { ? inbox = yes ? location = ? mailbox Drafts { ???

Hi Mark, Just to let you know that we are running dovecot with AD. (and I guess: *many* people are running that combination) It worked without issues, we are using in dovecot-ldap.conf.ext: > auth_bind = yes this user/passwd filter: > = (&(objectclass=person)(sAMAccountName=%n)(!(userAccountControl=514))) > dn = cn=search_dovecit,cn=users,dc=company,dc=com > dnpass =

Just wondering if there is an easy way to have dovecot do a blacklist lookup as a negative authentication so that if the IP is on a blacklist then authentification fails even if they get the password right. If this works I have a blacklist everyone can use.