similar to: Authentification fails in dovecot 2.3.0.1

In weakforced you have webserver("0.0.0.0:8084", "THIS-IS-THE-PASSWORD-FOR-WFORCE") Thus, you make the base64 blob as ~$ echo -n wforce:THIS-IS-THE-PASSWORD-FOR-WFORCE | base64 d2ZvcmNlOlRISVMtSVMtVEhFLVBBU1NXT1JELUZPUi1XRk9SQ0U= And in dovecot you put auth_policy_server_api_header = Authorization Basic d2ZvcmNlOlRISVMtSVMtVEhFLVBBU1NXT1JELUZPUi1XRk9SQ0U Aki > On 7

Here is my "dovecot -n": # 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.1 (d33dca2) # OS: Linux 4.4.0-116-generic x86_64 Ubuntu 16.04.4 LTS auth_debug = yes auth_username_format = %n auth_verbose = yes hostname = volker-wysk.de log_path = /var/log/dovecot.log mail_debug = yes mail_location = mdbox:~/lib/Dovecot-Mail managesieve_notify_capability = mailto

I took suggestions from https://forge.puppet.com/fraenki/wforce to set these in /etc/dovecot/conf.d/95-auth.conf auth_policy_server_url = http://localhost:8084/ auth_policy_hash_nonce = our_password auth_policy_server_api_header = "Authorization: Basic hash_from_running_echo-n_base64" auth_policy_server_timeout_msecs = 2000 auth_policy_hash_mech = sha256 auth_policy_request_attributes =

On Sun, 22 Nov 2020 at 15:08, Odhiambo Washington <odhiambo at gmail.com> wrote: > Hi, > > I have setup samba4 as AD and hoping to have dovecot authenticate users > against it. I am facing challenges though and I am unable to figure it out. > I could do with a third eye to help me spot what is wrong. > > > root at adc0:/etc# doveadm auth test -x service=imap >

So for auth_policy_server_api_header. is the value of our_password come from the hashed response or the plain-text password? What else am I doing wrong? Mar 7 09:20:53 olddsm wforce[17763]: WforceWebserver: HTTP Request "/" from 127.0.0.1:56416: Web Authentication failed curl -X POST -H "Content-Type: application/json" --data '{"login?:?ouruser?, "remote":

Hi, I have setup samba4 as AD and hoping to have dovecot authenticate users against it. I am facing challenges though and I am unable to figure it out. I could do with a third eye to help me spot what is wrong. root at adc0:/etc# doveadm auth test -x service=imap odhiambo at newideatest.local Password: passdb: odhiambo at newideatest.local auth failed extra fields: temp Warning: auth-client:

Hi, at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can we expect packages for v2.2.27 to appear there? -- Regards mks

I don't see it, and can't really think of a good reason why it would happen. This happens in configure? And the first thing you ran was configure, right? No autogen.sh or autoconf/automake? -bash-4.1# cat /etc/redhat-release CentOS release 6.8 (Final) -bash-4.1# uname -a Linux test-centos6.dovecot.net 2.6.32-642.6.1.el6.x86_64 #1 SMP Wed Oct 5 00:36:12 UTC 2016 x86_64 x86_64 x86_64

?? Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. ?I followed the info on repo.dovecot.org, and first it started bitching about lmtp (dovecot: master: Fatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such

Am 15.07.2017 um 20:26 schrieb Aki Tuomi: > Hi! > Just thought I'd remind about few things, > > since v2.2.22 you can use doveadm -fjson, to print data in json format, which might be easier to parse. As for Debian stable (dovecot 2.2.27) -f json is missing from the manpage. > since v2.2.22 you can use doveadm HTTP API to get the statistics over HTTP. > > since v2.2.27

I've successfully implemented the mail_crypt plugin on v2.2.27 and it's working like a champ, but some of our administrative operations require access to Maildir messages in plaintext. I've found numerous threads detailing help with mail_crypt setup, but none of my research has yielded a method of decrypting the stored messages. Relevant plugin config: mail_crypt_curve =

I am trying to use dovecot without ssl in centos 7. It works with imap but I am not able to make it work with pop3. Pop3 only works with ssl=yes. I can use dovecot in centos 4 ok.? I get the same error with thunderbird and outlook. But for some reason it works when I telnet to port 110 and do retr 1. I was able to work pam and shadow passwords. this is the output that does not work with tls

http://repo.dovecot.org/ <http://repo.dovecot.org/> Sami > On 8 Aug 2018, at 10.27, Simeon Ott <simeon.ott at onnet.ch> wrote: > > Okay, this seems to be due to the fact that the option ?use_globals_only" is supported only in v2.2.31+ > We are on Debian jessie with dovecot v2.2.13 ? even an upgrade to current stable stretch won?t help (dovecot v2.2.27). So we will

Hello Aki, maybe I misunderstood you, but both adding an "ssl = yes" line to this section of dovecot.conf, and commenting out the whole "four lines starting at "inet_listener imaps" do not have any effect : service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } this is the error I still get after

Hello. Few days ago upgraded from v2.2.26.0 >v2.2.27 and now windows 10, with any outlook version (2007,2010,2013,2016) doesn't connect IMAP SSL: Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key

Dear Everybody: May I ask how to configure dovecot otp one-time verification login, that is, after the user logs in to the mailbox with the password + otp, he can send and receive emails without entering the password + otp again? # This is my settings: # /etc/dovecot/conf.d/10-auth.conf disable_plaintext_auth = yes auth_cache_size = 10M auth_failure_delay = 5 secs

On February 3, 2018 3:39:56 AM GMT+01:00, Volker Wysk <post at volker-wysk.de> wrote: >Hi > >I'm changing from fetchmail to getmail, in order to fetch my mail from >several mail servers and deliver it to my local dovecot server. >Fetchmail supports LMTP, getmail doesn't. So I'm making getmail call >dovecot-lda for delivering the mail. But now, the incoming mail

> On December 3, 2016 at 11:20 PM Ricardo Machini <ricardomachini at gmail.com> wrote: > > > Helo Timo, > > I tried to compile and got one error on Centos 6.8: > > checking that generated files are newer than configure... done > configure: error: conditional "SSL_VERSION_GE_102" was never defined. > Usually this means the macro was only invoked

As a way to try and avoid using "prefix = INBOX." ad infinitum for the inbox namespace, I'm looking for ways to move on to "prefix =" for new mail accounts, and grandfather the existing ones. Previously running Courier-IMAP, now Dovecot, I looked at https://wiki.dovecot.org/Namespaces#Backwards_Compatibility:_Courier_IMAP and decided it's too risky to go down that

This happens on configure, I only ran ./configure. This error is logged to stderr: [root at host1 dovecot]# wget https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz [root at host1 dovecot]# tar xzf dovecot-2.2.27.tar.gz [root at host1 dovecot]# cd dovecot-2.2.27 [root at host1 dovecot-2.2.27]# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo configure: error: