Agreed, although it doesn't apply to sending emails from non European
citizens, only mailboxes containing European citizens' emails.
It's only enforceable if the citizenship of the holder of the mailbox is
known.
However, the assertion that if you are a company you are required to
delete old e
recent versions of denyhosts offer protection for dovecot imap if
enabled by scanning logs and adding firewall rules as well as hosts.deny
rules.
that may help
On 17/11/2023 10:18, Nick Lockheart wrote:
My original reason for asking was, in addition to setting up a new mail server,
there was a
On 20/01/2019 11:29, Stephan Bosch wrote:
Op 20/01/2019 om 00:21 schreef Tim Dickson via dovecot:
On 19/01/2019 17:54, Stephan Bosch wrote:
relevant info from /var/log/dovecot.log (domain changed for privacy)
Jan 19 09:27:09 lda(tim): Debug: Loading modules from directory:
/usr/lib64
On 19/01/2019 17:54, Stephan Bosch wrote:
Op 19/01/2019 om 10:51 schreef Tim Dickson via dovecot:
On 19/01/2019 08:01, Aki Tuomi wrote:
On 19 January 2019 at 02:07 Tim Dickson via dovecot <
dovecot@dovecot.org <mailto:dovecot@dovecot.org>> wrote:
i recently upgraded a
On 19/01/2019 10:02, Aki Tuomi wrote:
On 19 January 2019 at 11:51 Tim Dickson via dovecot <
dovecot@dovecot.org <mailto:dovecot@dovecot.org>> wrote:
On 19/01/2019 08:01, Aki Tuomi wrote:
>
>> On 19 January 2019 at 02:07 Tim Dickson via dovecot <
>> dovec
On 19/01/2019 08:01, Aki Tuomi wrote:
On 19 January 2019 at 02:07 Tim Dickson via dovecot <
dovecot@dovecot.org <mailto:dovecot@dovecot.org>> wrote:
i recently upgraded a server from dovecot 2.1 to 2.3
unfortunately sieve does not appear to be working. The user scripts have
not
i recently upgraded a server from dovecot 2.1 to 2.3
unfortunately sieve does not appear to be working. The user scripts have
not changed, and neither has the dovecont config. using managesieve
allows me to create new sieve files and setting one as default updates
the link in ~/ to point to the
