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 Giesbrec
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 lik
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
l
On 22 May 2017, at 10.07, Christoph Pleger wrote:
>
> Hello,
>
I am using sieve with notification of the original recipient in the case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifica
Hi,
I'm an Apache James committer and we are curious to use imaptest in
order to validate our IMAP protocol implementation.
I'm using the nightlybuild : imaptest-20170506
I follow the examples given in the /T/ /est IMAP server compliancy/
examples https://imapwiki.org/ImapTest/Examples.
An
