Ken,
Both of my production servers see the exact same problem. What was worse I was
seeing around 100K failed attempts to login to my root user. A bit of research
and now my firewall ignores any attempt from PRC.
Sort of a cost of doing business
Steve Hanselman
Sent from my iPad
> On Jan 7,
On Fri, 2022-01-07 at 23:59 -0500, Dave McGuire wrote:
> On 1/7/22 11:58 PM, Ken Wright wrote:
> > > > When I try to log in to my mail server (ubuntu 20.04, Postfix
> > > > 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream
> > > > returned no data”. At least to me, that's not particu
On 1/7/22 11:58 PM, Ken Wright wrote:
When I try to log in to my mail server (ubuntu 20.04, Postfix
3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream
returned no data”. At least to me, that's not particularly
informative. Is it any more informative to anyone else?
The last t
On Fri, 2022-01-07 at 23:50 -0500, Dave McGuire wrote:
> On 1/7/22 11:46 PM, Ken Wright wrote:
> > When I try to log in to my mail server (ubuntu 20.04, Postfix
> > 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream
> > returned no data”. At least to me, that's not particularly
> > in
On 1/7/22 11:46 PM, Ken Wright wrote:
When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13,
Dovecot 2.3.7.2) I get a response saying "Source stream returned no
data”. At least to me, that's not particularly informative. Is it any
more informative to anyone else?
The last tim
When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13,
Dovecot 2.3.7.2) I get a response saying "Source stream returned no
data”. At least to me, that's not particularly informative. Is it any
more informative to anyone else?
Ken
On 1/7/22 11:35 PM, Ken Wright wrote:
My Dovecot issues continue. Right now I see at least two issues:
first, my logs consistently show non-users trying (and failing) to
log in, and I'm still unable to log in from my email client
(Evolution or Roundcube, either one).
I'll post about the second
As Dave mentioned, Fail2ban.
You'll likely want to set up graduated responses with fail2ban so the
more they try, the longer it takes for them to get off the ban list.
Best
N
On 1/7/22 20:35, Ken Wright wrote:
On Fri, 2022-01-07 at 23:27 -0500, Dave McGuire wrote:
On 1/7/22 11:24 PM, Ken
On Fri, 2022-01-07 at 23:27 -0500, Dave McGuire wrote:
> On 1/7/22 11:24 PM, Ken Wright wrote:
> > My Dovecot issues continue. Right now I see at least two issues:
> > first, my logs consistently show non-users trying (and failing) to
> > log in, and I'm still unable to log in from my email client
On 1/7/22 11:24 PM, Ken Wright wrote:
My Dovecot issues continue. Right now I see at least two issues:
first, my logs consistently show non-users trying (and failing) to log
in, and I'm still unable to log in from my email client (Evolution or
Roundcube, either one).
I'll post about the second
My Dovecot issues continue. Right now I see at least two issues:
first, my logs consistently show non-users trying (and failing) to log
in, and I'm still unable to log in from my email client (Evolution or
Roundcube, either one).
I'll post about the second issue later; right now I wonder why I'm
> user_query = SELECT maildir, 2000 AS uid, 2000 AS gid FROM mailbox
> WHERE username = '%u' AND active='1'
If you are using a static uid/gid it is not needed to have it include it in
queries.
You can set them in the config with:
mail_uid = 2000
mail_gid = 2000
And then shorten the query
On Fri, Jan 7, 2022 at 1:34 PM John Fawcett wrote:
> On 07/01/2022 21:03, Ken Wright wrote:
> > On Fri, 2022-01-07 at 18:50 +0100, John Fawcett wrote:
> >> it may or may not be related to the tls issue, but I think you will
> >> want to investigate that message about the SQL query syntax error.
>
Hi, after updating from dovecot.x86_64 2:2.3.16-2 to 2:2.3.17.1-1 on
AlmaLinux 8 my dovecot replication stopped working.
Log is full of
Error: doveadm server disconnected before handshake: Received invalid
SSL certificate: unable to get certificate CRL: /CN=my.domain.redacted
(check ssl_client_ca_*
On 07/01/2022 21:03, Ken Wright wrote:
On Fri, 2022-01-07 at 18:50 +0100, John Fawcett wrote:
it may or may not be related to the tls issue, but I think you will
want to investigate that message about the SQL query syntax error.
You are not going to be able to login if the query is giving errors
On Fri, 2022-01-07 at 18:50 +0100, John Fawcett wrote:
>
> it may or may not be related to the tls issue, but I think you will
> want to investigate that message about the SQL query syntax error.
> You are not going to be able to login if the query is giving errors.
> Check the log doesn't reveal
On 07/01/2022 18:31, Ken Wright wrote:
On Fri, 2022-01-07 at 10:02 +0100, Christian Kivalo wrote:
On January 7, 2022 9:51:20 AM GMT+01:00, Ken Wright
wrote:
I reinstalled Dovecot this evening, because I haven't been able to
receive emails recently. After configuring and adjusting for the use
You have to enable ssl logging check the configs!
> -Original Message-
> From: dovecot On Behalf Of Ken Wright
> Sent: Friday, January 07, 2022 6:32 PM
> To: Christian Kivalo ; dovecot@dovecot.org
> Subject: Re: TLS connection closed unexpectedly
>
> On Fri, 2022-01-07 at 10:02 +0100, Ch
On Fri, 2022-01-07 at 10:02 +0100, Christian Kivalo wrote:
>
>
> On January 7, 2022 9:51:20 AM GMT+01:00, Ken Wright
> wrote:
> > I reinstalled Dovecot this evening, because I haven't been able to
> > receive emails recently. After configuring and adjusting for the use
> > of PostfixAdmin, I ge
Thank you Aki and Juergen!
The default sieve location was different than mine, /home/vmail/
name.firstn...@mail.xxx.fr insted of /home/vmail/name.firstname
The solution :
vi /etc/dovecot/conf.d/90-sieve.conf
sieve = file:/home/vmail/%n/sieve;active=/home/vmail/%n/.dovecot.sieve
Cheers
Samuel
On 07/01/2022 14:01, Sam Kuper wrote:
You say you cannot see it, but I gave an example below, in my previous
email:
Secondly, a person sending an email to a mailing list might very well
consent for the mailing list's recipients to receive the content,
subject, and reply address of that email
On Wed, Jan 05, 2022 at 07:00:19PM +0100, John Fawcett wrote:
> On 05/01/2022 18:36, Sam Kuper wrote:
>> On Wed, Jan 05, 2022 at 06:00:31PM +0100, John Fawcett wrote:
>>> my understanding of the GDPR legislation is that it defines what is
>>> considered lawful processing. One of those items that ma
> On 07/01/2022 13:20 Sam R wrote:
>
>
> Hello,
>
> I have an issue with Sieve plugin, I can drive rules remotely with
> sieve://myserver.fr:4190/?tls=YES (http://myserver.fr:4190/?tls=YES), the
> rules are well created under /home/vmail/name.firstname, but these are never
> executed.
>
>
Am Freitag, Januar 07, 2022 12:20 CET, schrieb Sam R :
Hello, I have an issue with Sieve plugin, I can drive rules remotely with
sieve://myserver.fr:4190/?tls=YES, the rules are well created under
/home/vmail/name.firstname, but these are never executed.
I have also read
https://doc.dovecot.o
Hello,
I have an issue with Sieve plugin, I can drive rules remotely with sieve://
myserver.fr:4190/?tls=YES, the rules are well created under
/home/vmail/name.firstname, but these are never executed.
I have also read
https://doc.dovecot.org/configuration_manual/sieve/troubleshooting/, but I
don'
On January 7, 2022 9:51:20 AM GMT+01:00, Ken Wright
wrote:
>I reinstalled Dovecot this evening, because I haven't been able to
>receive emails recently. After configuring and adjusting for the use
>of PostfixAdmin, I get the following error message in Evolution:;
>
>Failed to open folder.
>Th
I reinstalled Dovecot this evening, because I haven't been able to
receive emails recently. After configuring and adjusting for the use
of PostfixAdmin, I get the following error message in Evolution:;
Failed to open folder.
The reported error was "Failed to authenticate: TLS connection closed
un
27 matches
Mail list logo
