On 12/04/2011 16:13, Timo Sirainen wrote:
On Tue, 2011-04-12 at 16:03 +0200, mail...@securitylabs.it wrote:
On 12/04/2011 15:51, Rick Romero wrote:
I had the same issue - Dovecot has it's own method of updating
lastauth and doesn't put the IP address in the field, but 'pop' or
'imap'.
That's w
On Tue, 2011-04-12 at 16:03 +0200, mail...@securitylabs.it wrote:
> On 12/04/2011 15:51, Rick Romero wrote:
> > I had the same issue - Dovecot has it's own method of updating
> > lastauth and doesn't put the IP address in the field, but 'pop' or
> > 'imap'.
>
> That's would be fine, I don't need
On 12/04/2011 15:51, Rick Romero wrote:
I had the same issue - Dovecot has it's own method of updating
lastauth and doesn't put the IP address in the field, but 'pop' or
'imap'.
That's would be fine, I don't need the IP and with 1.2.16 it works (no
IP, only pop3/imap logged). But with 2.0.11
I had the same issue - Dovecot has it's own method of updating
lastauth and doesn't put the IP address in the field, but 'pop' or
'imap'. I'd rather have the IP. It was easier to just write my own
postauth script.
I've added a 'type' field so I can keep track of pop/imap/smtp
separately
Hello, I'm migrating many accounts to a new server with vpopmail 5.4.33
and dovecot 2.0.11.
I've already vpopmail 5.4.32 and dovecot 1.2.16 on others servers
running without problems.
With dovecot 2.0.11 my lastauth file is not updated. This file usually
is update on any access (smtp, pop3,
