r, it appears in a comment line in
/etc/dovecot/conf.d/10-master.conf
Should that line be uncommented?
Much thanks.
Max Pyziur
p...@brama.com
Report of dovecot -n:
pyz@pangea ~> dovecot -n
# 2.1.1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-358.2.1.el6.x86_64 x86_64 CentOS release 6.
your /etc/hosts.deny
file, using tcp_wrappers to prevent intrusion/brute force attacks on
service that have open ports in the firewall.
Thanks,
Max Pyziur
p...@brama.com
On Sat, 6 Apr 2013, Reindl Harald wrote:
Am 06.04.2013 22:55, schrieb Max Pyziur:
On Sat, 6 Apr 2013, Reindl Harald wrote:
has someone a script which can filter out dictionary attacks
from /var/log/maillog and notify about the source-IPs?
i know about fail2ban and so on, but i would like
> On 5.4.2013, at 18.19, Max Pyziur wrote:
>
>> So my question relates to the second part of the configuration examples
>> in the links above:
>>
>> service tcpwrap {
>> unix_listener login/tcpwrap {
>>group = $default_login_user
>>
On Mon, 8 Apr 2013, Timo Sirainen wrote:
On 8.4.2013, at 1.31, "Max Pyziur" wrote:
However, once I make the changes to the configuration files, I get the
following error when restarting dovecot:
root@brama /etc/dovecot/conf.d> service dovecot restart
Stopping
On Sun, 7 Apr 2013, Max Pyziur wrote:
On Mon, 8 Apr 2013, Timo Sirainen wrote:
On 8.4.2013, at 1.31, "Max Pyziur" wrote:
However, once I make the changes to the configuration files, I get the
following error when restarting dovecot:
root@brama /etc/dovecot/conf.d> service do
> On 5.4.2013, at 18.19, Max Pyziur wrote:
>
>> So my question relates to the second part of the configuration examples
>> in the links above:
>>
>> service tcpwrap {
>> unix_listener login/tcpwrap {
>>group = $default_login_user
>>
he firewall has ports 110 and 143 open,
but I'm blocking a particular host through /etc/hosts.deny
then I should not be able to telnet to either port 110 or 143; both
requests should be blocked from the originating IP, no?
Much thanks for your help,
Max Pyziur
p...@brama.com
What are you using
On Fri, 21 Nov 2014, Timo Sirainen wrote:
Apparently this list has somehow broken.. Not really sure what the problem is,
lets see what happens to this mail.
Any chance of putting "[dovecot]" back in the subject line?
Thanks.
Max Pyziur
p...@brama.com
