On Fri, 12 Apr 2019, mj wrote:
What we do is: use https://github.com/trick77/ipset-blacklist to block IPs
(from various existing blacklists) at the iptables level using an ipset.
"www.blocklist.de" is a nifty source. Could you suggest other publically
available blacklists?
That way, the
On 12 April 2019 at 22:01 Robert Kudyba via dovecot <
dovecot@dovecot.org> wrote:
>
On 12 April 2019 21:45 Robert Kudyba via dovecot <
dovecot@dovecot.org>
wrote:
>
> > On 12 April 2019 21:45 Robert Kudyba via dovecot
> wrote:
> >
> >
> > > You are running some kind of proxy in front of it.
> >
> > No proxy. Just sendmail with users using emacs/Rmail or
> Webmail/Squirrelmail.
> >
> > > If you want it to show real client IP, you need to enable forwarding
>
> On 12 April 2019 21:45 Robert Kudyba via dovecot wrote:
>
>
> > You are running some kind of proxy in front of it.
>
> No proxy. Just sendmail with users using emacs/Rmail or Webmail/Squirrelmail.
>
> > If you want it to show real client IP, you need to enable forwarding of
> > said
>
> You are running some kind of proxy in front of it.
No proxy. Just sendmail with users using emacs/Rmail or
Webmail/Squirrelmail.
> If you want it to show real client IP, you need to enable forwarding of
> said data. With dovecot it's done by setting
>
> login_trusted_networks =
On Fri, Apr 12, 2019 at 11:14 AM Aki Tuomi
wrote:
>
> > On 12 April 2019 21:09 Mark Moseley via dovecot
> wrote:
> >
> >
> > TL;DR:
> >
> > Can director_username_hash use %{userdb:...} or %{passdb:...} ?
> >
> >
> >
> > This is on Ubuntu Precise, running
> On 12 April 2019 21:09 Mark Moseley via dovecot wrote:
>
>
> TL;DR:
>
> Can director_username_hash use %{userdb:...} or %{passdb:...} ?
>
>
>
> This is on Ubuntu Precise, running dovecot 2.2.36. It's a fully production,
> director-ized env, so assume
TL;DR:
Can director_username_hash use %{userdb:...} or %{passdb:...} ?
This is on Ubuntu Precise, running dovecot 2.2.36. It's a fully production,
director-ized env, so assume everything is working correctly. Happy to post
doveconf if it's relevant but
> On 12 April 2019 18:11 Robert Kudyba via dovecot wrote:
>
>
> > Probably there's an existing solution for both problems (subsequent
> > attempts and dnsbl):
> >
> > >
> >
On Fri, 12 Apr 2019, @lbutlr wrote:
All users except one: Said user asked if it would be possible to
disable subaddressing (localuser+folder at example.com) again.
The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox
item.
I thought it was sieve that did this?
I'm resurrecting this again because I'm getting pretty close to possibly
being ready to install a brand new dovecot server (finally), but I still
need for dovecots LMTP to add the x-original-to header.
So... was this completed quietly, or is support for it still not there?
Thanks,
Charles
On
Hi,
I'm experiencing serious issues when using doveadm sync not working at
all or do not properly sync. I wanted to use this for migrating external
mailboxes to my server (in order to overcome the time when some
servers/clients still use the old server and some already the my server).
I tried to
On 12 Apr 2019, at 09:06, Andreas Thienemann via dovecot
wrote:
>
> All users except one: Said user asked if it would be possible to disable
> subaddressing (localuser+fol...@example.com) again.
>
> The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox item.
I thought it was
>
> Probably there's an existing solution for both problems (subsequent
> attempts and dnsbl):
>
> >
>
Hi,
I have a dovecot 2.3.2.1 instance running here that is getting userdb and
passdb data from a SQL database. This was a cyrus server migrated over and
all users are happy.
All users except one: Said user asked if it would be possible to disable
subaddressing (localuser+fol...@example.com)
> Le 11 avr. 2019 à 12:23, Marc Roos via dovecot a écrit :
>
>
>
> Say for instance you have some one trying to constantly access an
> account
>
>
> Has any of you made something creative like this:
>
> * configure that account to allow to login with any password
> * link that account
Citát "B. Reino via dovecot" :
On 2019-04-12 11:05, azurit--- via dovecot wrote:
Citát "B. Reino via dovecot" :
On 2019-04-12 07:43, azurit--- via dovecot wrote:
Hi,
recently, we had a problem on one of our mail servers and, after
reboot, HDD with emails wasn't mounted into system. Until
On 2019-04-12 11:05, azurit--- via dovecot wrote:
Citát "B. Reino via dovecot" :
On 2019-04-12 07:43, azurit--- via dovecot wrote:
Hi,
recently, we had a problem on one of our mail servers and, after
reboot, HDD with emails wasn't mounted into system. Until we fixed
it,
LOTS of users
On 12 April 2019 15:48 @lbutlr via dovecot <
dovecot@dovecot.org> wrote:
Are there any examples of the utility of doveadm stats?
in the man page:
dump accepts following types: command,
Are there any examples of the utility of doveadm stats?
in the man page:
> dump accepts following types: command, session, user, domain, ip and
>global.
>
>Filter can be
>
>user=
> Match given user.
I've tried the following commands after looking at the
Hi,
What we do is: use https://github.com/trick77/ipset-blacklist to block
IPs (from various existing blacklists) at the iptables level using an ipset.
That way, the known bad IPs never even talk to dovecot, but are dropped
immediately. We have the feeling it helps a lot.
MJ
On 4/12/19
Looking further at tcpdumps of the Dovecot->Solr traffic and Solr
metrics it doesn't seem like there's anything suspicious apart from the
TCP windows running full and Dovecot backing of ... until it times out
and close the connection.
>From my understanding of how Dovecot operates towards Solr
You can use
plugin {
acl_user = %u
}
Aki
On 12 April 2019 12:35 Usuario prueba via dovecot wrote:
I think is an ACL problem for master user. My
I think is an ACL problem for master user. My master user is named "administrator" (static password files), all other users have ldap backend, and I tried to add this to acl file using vim
* user=administrator lr
But still does not work. I have read several times
Citát "B. Reino via dovecot" :
On 2019-04-12 07:43, azurit--- via dovecot wrote:
Hi,
recently, we had a problem on one of our mail servers and, after
reboot, HDD with emails wasn't mounted into system. Until we fixed it,
LOTS of users logged in (Dovecot allowed login and recreated
directory
Citát "B. Reino via dovecot" :
On 2019-04-12 07:43, azurit--- via dovecot wrote:
Hi,
recently, we had a problem on one of our mail servers and, after
reboot, HDD with emails wasn't mounted into system. Until we fixed it,
LOTS of users logged in (Dovecot allowed login and recreated
directory
On 12/04/2019 08:42, Aki Tuomi via dovecot wrote:
On 12.4.2019 10.34, James via dovecot wrote:
On 12/04/2019 08:24, Aki Tuomi via dovecot wrote:
Weakforced uses Lua so you can easily integrate DNSBL support into it.
How does this help Dovecot block?
A link to some documentation or example
On 12.4.2019 10.34, James via dovecot wrote:
> On 12/04/2019 08:24, Aki Tuomi via dovecot wrote:
>
>> Weakforced uses Lua so you can easily integrate DNSBL support into it.
>
> How does this help Dovecot block?
> A link to some documentation or example perhaps?
>
>
I am trying to migrate via imapsync a Dovecot mail server (host1) to Office 365 (hosts2) (just a test, I love Dovecot).
Imapsync, using dovecot master user, exact command I am using:
imapsync --host1 myhost.mydomain --user1 testu...@mydomain.com*administrator --password1 "X" --host2
On 12/04/2019 08:24, Aki Tuomi via dovecot wrote:
Weakforced uses Lua so you can easily integrate DNSBL support into it.
How does this help Dovecot block?
A link to some documentation or example perhaps?
We will not add DNSBL support to dovecot at this time.
Is there a reason why you
On 12.4.2019 10.21, James via dovecot wrote:
> On 11/04/2019 14:33, Anton Dollmaier via dovecot wrote:
>
>>> Which is why a dnsbl for dovecot is a good idea. I do not believe the
>>> agents behind these login attempts are only targeting me, hence the
>>> addresses should be shared via a dnsbl.
On 11/04/2019 14:33, Anton Dollmaier via dovecot wrote:
Which is why a dnsbl for dovecot is a good idea. I do not believe the
agents behind these login attempts are only targeting me, hence the
addresses should be shared via a dnsbl.
Probably there's an existing solution for both problems
On 2019-04-12 07:43, azurit--- via dovecot wrote:
Hi,
recently, we had a problem on one of our mail servers and, after
reboot, HDD with emails wasn't mounted into system. Until we fixed it,
LOTS of users logged in (Dovecot allowed login and recreated
directory structure of mailboxes) and saw
On 11/04/2019 23:28, sergio via dovecot wrote:
> Hello.
>
> I've just tested my system that runs dovecot 2.3.4.1 on debian buster
> with testssl.sh (https://testssl.sh/) and is says:
>
> Secure Renegotiation (CVE-2009-3555) not vulnerable (OK)
> Secure Client-Initiated Renegotiation
34 matches
Mail list logo
