Hello,
I'm looking for something maybe similar to master password but for
final users and I don't know if there is already a way I could do it
with dovecot.
I have accounts that are used by a set of users who know their
password. But I now want to remove this shared password and the users
Hi,
anyone has this problem?
Il 03/06/2014 11:07, Giovanni Mancuso ha scritto:
Hi,
I deliver a test email (with 4 spaces in subject) into a maildir:
Return-Path: u...@example.com
Delivered-To: u...@example.com
Received: from suse11 ([10.0.8.7])
by suse11 (Dovecot) with LMTP id
On 2014-06-17 04:50, deano-dove...@areyes.com wrote:
I'm trying to avoid switching the userdb from a nice simple static
setup to something else to enable replication. Is there anyone using
replication with a virtual user configuration ? How did you do it ?
Actually, anyone doing replication at
Hi!
I am trying to use the static userdb with virtual users stored in ldap
and the replicator plugin. What is the best way to implement this? I was
not able to find documentation about it.
Thanks!
after having my own dnsbl feeded by a honeypot and even
mod_security supports it for webservers i think dovecot
sould support the same to prevent dictionary attacks from
known bad hosts, in our case that blacklist is 100%
trustable and blocks before SMTP-Auth while normal RBL's
are after SASL
i
On 17/06/2014 18:16, Reindl Harald wrote:
after having my own dnsbl feeded by a honeypot and even
mod_security supports it for webservers i think dovecot
sould support the same to prevent dictionary attacks from
known bad hosts, in our case that blacklist is 100%
trustable and blocks before
Am 17.06.2014 19:43, schrieb Giles Coochey:
On 17/06/2014 18:16, Reindl Harald wrote:
after having my own dnsbl feeded by a honeypot and even
mod_security supports it for webservers i think dovecot
sould support the same to prevent dictionary attacks from
known bad hosts, in our case that
On 17/06/2014 18:56, Reindl Harald wrote:
Am 17.06.2014 19:43, schrieb Giles Coochey:
On 17/06/2014 18:16, Reindl Harald wrote:
after having my own dnsbl feeded by a honeypot and even
mod_security supports it for webservers i think dovecot
sould support the same to prevent dictionary attacks
Am 17.06.2014 20:23, schrieb Giles Coochey:
On 17/06/2014 18:56, Reindl Harald wrote:
Am 17.06.2014 19:43, schrieb Giles Coochey:
On 17/06/2014 18:16, Reindl Harald wrote:
after having my own dnsbl feeded by a honeypot and even
mod_security supports it for webservers i think dovecot
sould
On 17/06/2014 19:32, Reindl Harald wrote:
Am 17.06.2014 20:23, schrieb Giles Coochey:
On 17/06/2014 18:56, Reindl Harald wrote:
Am 17.06.2014 19:43, schrieb Giles Coochey:
On 17/06/2014 18:16, Reindl Harald wrote:
Iptables has a log option
please read again what you quoted
iptables logs
Am 17.06.2014 20:39, schrieb Giles Coochey:
On 17/06/2014 19:32, Reindl Harald wrote:
Am 17.06.2014 20:23, schrieb Giles Coochey:
On 17/06/2014 18:56, Reindl Harald wrote:
Am 17.06.2014 19:43, schrieb Giles Coochey:
On 17/06/2014 18:16, Reindl Harald wrote:
Iptables has a log option
On -10.01.-28163 20:59, Reindl Harald wrote:
i admit that i am not a C/C++-programmer, but i think
doing the DNS request and in case it has a result block
any login attemt should be not too complex
Can't say that I actually ever *did* it, but according to the docs, the
following should work:
Am 17.06.2014 21:04, schrieb Jochen Bern:
On -10.01.-28163 20:59, Reindl Harald wrote:
i admit that i am not a C/C++-programmer, but i think
doing the DNS request and in case it has a result block
any login attemt should be not too complex
Can't say that I actually ever *did* it, but
On 6/17/2014 7:16 PM, Reindl Harald wrote:
after having my own dnsbl feeded by a honeypot and even
mod_security supports it for webservers i think dovecot
sould support the same to prevent dictionary attacks from
known bad hosts, in our case that blacklist is 100%
trustable and blocks before
Trying to get ACLs working, very basic setup:
Virtual users are put into different acl_group via passdb.
u:{PLAIN}B::userdb_acl_groups=g
The global acl file restricts what they can do.
* group-override=g
* group=g lr
Shouldn't this mean, that the group rights override the user
Hi
command im using command bellow on destination server rtying to make
keep it in sync after initialy doing doveadm backup -R
doveadm -Dv -o imapc_host=src.srv -o imapc_user=t...@domain.tld
-opop3c_user=t...@domain.tld -o imapc_password='pass' -o
pop3c_password='pass' -o mail_fsync=never -o
16 matches
Mail list logo