From: Steve Dondley
> I have no idea what is triggering it for so many different users from legit
> email addresses. Still investigating. But this appears to be a fail2ban
> problem, not a dovecot problem.
My logs are filled with failed authentication from Outlook clients. The clients
seem to b
Yeah I think I figured it out. It looks like someone set up their phone with
bad password and when they got on the WiFi network it got everyone else on the
network banned for 10 min. I’ve whitelisted the ip for now. I think the guy was
traveling between different offices making it look like it w
Hi,
> On 22. Jan 2024, at 20.00, Achim Stahlberger
> wrote:
>
> Hello,
>
> we see this problem when doveadm-server is under load.
>
> We enabled doveadm http api with this config:
>
> service doveadm {
> inet_listener {
>port = 5
> }
> inet_listener http {
>port = 50001
>s
On Mon, Jan 22, 2024 at 04:28:09PM -0500, Steve Dondley via dovecot wrote:
> OK, I was chasing log ghosts. What was actually going on was fail2ban was
> kicking on for users and banning them for 10 min.
>
> I have no idea what is triggering it for so many different users from legit
> email addres
That lets me run sync jobs and get verbose output.
But I haven't managed to have a manuall-started sync that stalled.
It's only a small fraction of the sync jobs that stall,
even though at any given time there are usually several stalled
jobs running.
(Because the stalled jobs take much longer th
OK, I was chasing log ghosts. What was actually going on was fail2ban was
kicking on for users and banning them for 10 min.
I have no idea what is triggering it for so many different users from legit
email addresses. Still investigating. But this appears to be a fail2ban
problem, not a dovecot pr
On 1/22/2024 15:21:22, joe a wrote:
On 1/18/2024 18:30:06, Joe Acquisto wrote:
Trying to connect to managesieve server configured to port 4190. No go.
Roundcube is configured (thunderbird apparently having nothing
current), but selecting "Add Filter" (new since re-configured for
managesieve)
On 1/18/2024 18:30:06, Joe Acquisto wrote:
Trying to connect to managesieve server configured to port 4190. No go.
Roundcube is configured (thunderbird apparently having nothing current),
but selecting "Add Filter" (new since re-configured for managesieve)
produces "unable to connect to server
doveconf replication_dsync_parameters
then you can do
doveadm sync -u
Aki
> On 22/01/2024 21:05 EET Andy Balholm wrote:
>
>
> Is there a way to find out the exact command line that the
> replicator is using to invoke doveadm sync?
>
> Andy
>
> On Monday, January 22, 2024 10:55:12 AM PS
Is there a way to find out the exact command line that the
replicator is using to invoke doveadm sync?
Andy
On Monday, January 22, 2024 10:55:12 AM PST, Aki Tuomi wrote:
you could try running it manually from cli..
doveadm -D sync
Aki
On 22/01/2024 20:32 EET Andy Balholm wrote:
I'm not
you could try running it manually from cli..
doveadm -D sync
Aki
> On 22/01/2024 20:32 EET Andy Balholm wrote:
>
>
> I'm not sure how to do that, because I'm doing automatic replication,
> not running doveadm sync manually.
> I tried adding -D to replication_dsync_parameters,
> but that gav
I'm not sure how to do that, because I'm doing automatic replication,
not running doveadm sync manually.
I tried adding -D to replication_dsync_parameters,
but that gave me an error, because the -D was in the wrong place
on the command line.
(It should be doveadm -D sync, and it was ending up with
Hello,
we see this problem when doveadm-server is under load.
We enabled doveadm http api with this config:
service doveadm {
inet_listener {
port = 5
}
inet_listener http {
port = 50001
ssl = no
}
}
When doveadm server receives at lot of connects on port 5 the http
joe a skrev den 2024-01-22 17:40:
I don't grasp where you suggest placing "sieve"
# grep sieve /etc/dovecot/dovecot.conf
/etc/dovecot/dovecot.conf:protocols = imap lmtp sieve
means change
protocols = imap lmtp
to
protocols = imap lmtp sieve
Adding it to "protocols = imap lmtp" in 20-manag
On 1/21/2024 19:00:28, Benny Pedersen wrote:
joe a skrev den 2024-01-21 22:20:
Now, where are my notes? . . . oh, right, my bad.
check the maillist then :=)
protocols = imap lmtp
add sieve there
more help then i need "netstat -natpu | grep dovecot" output
tux ~ # netstat -natpu | grep dov
Based on your email I went back and took a closer took at the logs.
The client reported this happened at 11:58 of the 19th. I went back and took a
closer look and around 11:56 I found these entries in the log.
81218 Jan 18 11:56:56 ip-172-30-0-131 dovecot: imap(t.oli)<3739040>: Connection cl
> On 22/01/2024 17:16 EET Steve Dondley via dovecot wrote:
>
>
> > there is no user in the above line
> >
> >> Some characteristics of the problem that may offer a clue:
> >> * happening with multiple users, not just the same one
> >> * happens from different IP addresses.
> >
> > bots detec
> there is no user in the above line
>
>> Some characteristics of the problem that may offer a clue:
>> * happening with multiple users, not just the same one
>> * happens from different IP addresses.
>
> bots detected
The problem is happening to real users on real devices who are reporting ver
18 matches
Mail list logo
