similar to: doveadm fetch LARGE attachments and remove message

The problem we are facing is incorrect authentications being caught by firewall rules and IP?s getting blocked. We would like to be able to identify the problem account to help the domain admin track down the issue. Does anyone have another idea? We use sql user db so I thought of logging all login attempts to a table with timestamps and lookup the failed logins by timestamp. Regards, Bradley

In fact, looking again, dovecot should log the failure with username, if available. Aki On 24.05.2017 09:22, Aki Tuomi wrote: > As band-aid you could try looking at the SASL message, if you decode64 > it might contain the username in plain text. > > Aki > > > On 23.05.2017 17:44, Bradley Giesbrecht wrote: >> The problem we are facing is incorrect authentications being

dovecot 2.2.22 postfix 3.1.1 I?m seeing "SASL NTLM authentication failed: {long_hash}? in mail.log. Is there a way to log the SASL username? I think postfix is logging what Dovecot SASL is returning so I hope I am asking on the right list. Regards, Bradley Giesbrecht (pixilla)

Is the Dovecot Object Storage plugin still available for purchase? Clicking the store link [2] from this page [1] does not show any info about purchasing the plugin. [1] http://www.dovecot.fi/dovecot-object-storage-plugins-available-for-online-purchase/ [2] http://shop.dovecot.fi/ Regards, Bradley Giesbrecht (pixilla)

On Tue, Sep 15, 2015 at 12:31:25PM +0900, Timo Sirainen wrote: > On 12 Sep 2015, at 04:45, Bradley Giesbrecht <pixilla at macports.org> wrote: > > > > Is the Dovecot Object Storage plugin still available for purchase? > > > > It's available, but at least for now we're only selling it to big customers. Well how big? Would a univeristy with 25.000 users

As band-aid you could try looking at the SASL message, if you decode64 it might contain the username in plain text. Aki On 23.05.2017 17:44, Bradley Giesbrecht wrote: > The problem we are facing is incorrect authentications being caught by firewall rules and IP?s getting blocked. We would like to be able to identify the problem account to help the domain admin track down the issue. > >

Hi, I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot- sieve. Most everything seems to work but my webmail (roundcube) clients are not seeing their subscribed folders. Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2 I'm wondering if I have the two settings below configured correctly. dovecot.conf: mail_location =

Sorry if I missed the dovecot 2.0.betax managesieve sieve discussions. I have been looking in my list archive and haven't found a reference to this yet. I am trying to convert my dovecot.conf and am getting the following Fatal error: /** doveconf -n -c dovecot/dovecot.conf > dovecot.converted/dovecot.conf doveconf: Warning: Obsolete setting in dovecot/dovecot.conf:10:

The problem is that the SASL message contains NTLM(v2) message, so it would need to be decoded. We can see if there is something we can do about this. At the moment it's not possible to log this. Aki On 23.05.2017 03:23, Bradley Giesbrecht wrote: > dovecot 2.2.22 > postfix 3.1.1 > > I?m seeing "SASL NTLM authentication failed: {long_hash}? in mail.log. > > Is there a

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. +

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. +

I'm building a dovecot v2 Portfile for MacPorts. Where can I read up on dovecot v2 build and run dependencies? Are they the same as dovecot v1? Regards, Bradley Giesbrecht

Hello, dovecot-1.2.10 dovecot-sieve-0.1.14 dovecot-managesieve-0.11.11 I believe I patched dovecot successfully and compiled the dovecot and dovecot-sieve source tress. patching file README.managesieve patching file dovecot-example.conf patching file src/master/child-process.c patching file src/master/child-process.h patching file src/master/listener.c patching file

With dovecot2 and pigeonhole sieve/managesieve is it currently possible to store sieve rules in an sql database? If not is there a way to query all accounts; looking for things like active vacation rules? Regards, Bradley Giesbrecht

$ hg --cwd ./work/dovecot-antispam-plugin-50 glog -l3 --style compact @ 50[tip] 0319240072d8 2012-12-20 03:56 +0200 Eugene Paskevich <eugene at raptor.kiev.ua> | Made use of new DOVECOT_ABI_VERSION macro. ... $ configure; make Compiling signature-log.c (plugin)... signature-log.c:122: error: too many arguments to function ?dict_init? ... Reverting src/signature-log.c from r49 to

On 12 Sep 2015, at 04:45, Bradley Giesbrecht <pixilla at macports.org> wrote: > > Is the Dovecot Object Storage plugin still available for purchase? > > Clicking the store link [2] from this page [1] does not show any info about purchasing the plugin. > > [1] http://www.dovecot.fi/dovecot-object-storage-plugins-available-for-online-purchase/ > [2]

On 25 Sep 2015, at 17:56, Hans Morten Kind <Kind at adm.uib.no> wrote: > > On Tue, Sep 15, 2015 at 12:31:25PM +0900, Timo Sirainen wrote: >> On 12 Sep 2015, at 04:45, Bradley Giesbrecht <pixilla at macports.org> wrote: >>> >>> Is the Dovecot Object Storage plugin still available for purchase? >>> >> >> It's available, but at

http://imapwiki.org/SpecialUse Please fill out for all clients with all languages you know of. Knowing the mailbox names can be helpful with Dovecot's mailbox_alias plugin.

Hello List, I want to allow plain text passwords only on ssl/tls. Is it possible to have: auth default { mechanisms = cram-md5 ntlm ...... } and then over-ride this when connection is ssl/tls to allow plain and login? I have tried adding "mechanisms = plain login cram-md5 ntlm" to "protocol imaps{}" as an example but I get an error that the protocol does not

Hello, I recently was looking to update to dovecot 2.2 and I have been happily using the dovecot-antispam plugin in 2.1, but found that there have been some changes in dovecot that make this version not compile against 2.2. I'm wondering if Johannes you have any plans to update it, or if others have managed to figure out what is necessary to get it to work? The particular piece that I am