LMTP during dsync migration

[Jogi Hofmüller]

Hi,

Sorry for warming up this thread, but

Am 2014-07-31 13:34, schrieb Michael Grimm:

> In the meantime I use something like to block users during maintainance:
> 
> # temporary blocks
> passdb {
>   driver = passwd-file
>   deny = yes
>   args = /path/to/deny-users
> }
> 
> # regular
> passwd {
>   driver = sql
>   args = /path/to/dovecot-sql.conf
> }
> 
> /path/to/deny-users holds username to block.

This is really cool and works perfect for imap/pop.  It doesn't work for
LMTP, although it acknowledges that the user has been found in the deny
passdb:

Aug 21 13:01:00 klee dovecot: lmtp(pid): Connect from IP
Aug 21 13:01:00 klee dovecot: auth: passwd-file(fischer,IP): User found
from deny passdb
Aug 21 13:01:00 klee dovecot: lmtp(pid, fischer):
2UErAGzR9VMBPQAAGyzfLQ: sieve: msgid=unspecified: stored mail into
mailbox 'INBOX'
Aug 21 13:01:00 klee dovecot: lmtp(pid): Disconnect from 172.16.16.205:
Successful quit

Is this what is supposed to happen (since LMTP doesn't use authentication)?

Regards,
-- 
J.Hofmüller

ich zitiere wie Espenlaub.

https://twitter.com/TheGurkenkaiser/status/463444397678690304

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://dovecot.org/pipermail/dovecot/attachments/20140821/45d05ab4/attachment.sig>