Hi
I'm aware that there are several good reasons not to do what I want, but
in my use-case it would be an interesting feature. So please no
discussions about the reasonableness
I have some spamtrap SMTP servers (postfix). Currently SMTP AUTH is
disabled. But as I daily have thousands of AUTH trie
On 23.5.2019 10.12, Tobi via dovecot wrote:
> Hi
>
> I'm aware that there are several good reasons not to do what I want, but
> in my use-case it would be an interesting feature. So please no
> discussions about the reasonableness
>
> I have some spamtrap SMTP servers (postfix). Currently SMTP AU
On 23/05/2019 07:49, Steffen Kaiser via dovecot wrote:
> On Wed, 22 May 2019, John Fawcett via dovecot wrote:
>
> > an update when insert fails seems to be a MySQL specific extension to
> > standard Sql. So I think that it's clear that support for PostgreSql and
> > Sqlite needs to be implemented.
I have the same, create your own dns blacklist. And have fail2ban add
entries to it. The only problem I have on CentOS6 is that you need to
combine log files for this, but it should be do-able.
But I am also for this option, maybe it can be done via this userdb,
specify an account where auth
On 23 May 2019, at 01:44, Marc Roos via dovecot wrote:
> I would like to redirect sometimes a user to a 5GB garbage messages mailbox.
So you want to setup a service where random spammer/hacker can trivially DDOS
your system?
How many simultaneous 5GB streams can you handle? How much will your b
Marc,
as stated by Aki
> passdb {
> driver = static
> args = nopassword
>}
works fine and does what I want: accept any SMTP AUTH :-)
In my setup postfix has a catch-all anyway, so I can return
home=/dev/null in userdb
Saw the first tries on my server already. Just took 5min after enabling
SM
No, And you incorrectly assume, that I am not taking such things into
account.
But I can excuse this type of reply, due to the mere fact that IT is
saturated with "dumb fucks" (like to quote Zuckerberg). Don't the
Americans have a nice saying for this "Assumption is the mother of all
fuckup
I read the mailcrypt plugin document on the wiki and had couple
questions.
1. If I want per-user encryption am I correct I should configure global
keys with all related settings override in the userdb lookup?
2. If I do not want to encrypt some user accounts, is it enough to omit
the mail_cr
as stated by Aki
> passdb {
> driver = static
> args = nopassword
>}
works fine and does what I want: accept any SMTP AUTH :-)
(Brings back memories of good fun I had with patched Qpopper snare
feeding custom messages to the hacker.)
Another alternative is to use the checkpassword hook t
1. If I want per-user encryption am I correct I should configure
global keys with all related settings override in the userdb lookup?
2. If I do not want to encrypt some user accounts, is it enough to
omit the mail_crypt_global_private_key from the userdb lookup? In
other word, mail_plugins st
10 matches
Mail list logo