similar to: sieve in sql or reporting

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

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

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. > >

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

Looking at the wiki and man pages I am unsure how to fetch email attachments from a unix shell. I have an "doveadm search" that returns the messages that have the attachments I am after. Would I loop through an "doveadm fetch" and use a commandline imap client to save the attachments and move the message to the Trash? Or is there a doveadm command for this? Regards, Bradley

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

Hello folks, This morning I tried to open an old archive mail folder using Mutt. However, while fetching headers it aborted. Checking the dovecot log gave me this: @400000004fb21996267d37d4 imap(benv): Error: Cached message size smaller than expected (9115 < 9420) @400000004fb21996267e8bac imap(benv): Error: Maildir filename has wrong S value, renamed the file from

When we upgrade our kernels from 2.6.32.2 to 3.2.16 something strange has happened. On high traffic dovecot/auth looks like not responding. We found a lot of this lines at the log: dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable (...) and clients stop authorizing Some other errors follow in the wake of: dovecot: pop3: Error: Raw backtrace:

Hi all, I'm using dovecot 2.2.13 with virtual folders and fts-solr (see attached dovecot-n.conf). At using virtual folder with fts, the dovecot crashes with following panic: Aug 20 10:49:43 imap(...): Panic: file fts-search-serialize.c: line 63 (fts_search_deserialize_add_idx): assertion failed: (*idx < buf->used) Aug 20 10:49:43 imap(test4 at india.com): Error: Raw backtrace:

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

Getting complaints from people about pop/imap issues. some people are getting repaeted e-mail. Other are not able to delete their e-mails from an IMAP lcient. Current configuration /usr/dovecot2/sbin/dovecot -n # 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf # OS: FreeBSD 11.0-RELEASE-p2 amd64 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 100

I have version 2.0.0 and upgraded to 2.0.2 and after - this is happend: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e3425e] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e342b5] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e338d6] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e31cb1] -> dovecot/pop3(client_handle_input+0x8e) [0x804be7e] ->

Hello, I'm running Dovecot2 and trying to set up public mailboxes. I've got a virtual user system set up with postfix and using MySQL authentication. I'm wanting to create several public mailboxes for shared messages. I've followed the wiki and have the public folder created. I've got a folder /home/vmail/public/public1 public1 being the maildir of the public mailbox. I can

I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if dovecot2 already installed ===> Registering installation for dovecot2-2.2.31_1 as automatic