Your message dated Tue, 12 Jul 2011 22:06:50 -0400
with message-id <[email protected]>
and subject line Re: Bug#633701: just testing redirection and bouncing of bug
reports (includes attachements)
has caused the Debian Bug report #633701,
regarding just testing redirection and bouncing of bug reports (includes
attachements)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
633701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633701
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fail2ban
Version: 0.8.4-3.1~bugstry0
Severity: normal
ok -- testing! please disregard if you manage dto receive it
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable')
Architecture: amd64
(x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fail2ban depends on:
ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip
ii python 2.6.6-14 interactive high-level object-orie
ii python-central 0.6.17 register and build utility for Pyt
Versions of packages fail2ban recommends:
ii iptables 1.4.11.1-2 administration tools for packet fi
ii whois 5.0.11 an intelligent whois client
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent
pn python-gamin <none> (no description available)
-- Configuration Files:
/etc/fail2ban/action.d/iptables-multiport.conf changed:
[Definition]
actionstart = <actioncmd> -N fail2ban-<name>
<actioncmd> -A fail2ban-<name> -j RETURN
<actioncmd> -I <chain> -p <protocol> -m multiport --dports <port>
-j fail2ban-<name>
actionstop = <actioncmd> -D <chain> -p <protocol> -m multiport --dports <port>
-j fail2ban-<name>
<actioncmd> -F fail2ban-<name>
<actioncmd> -X fail2ban-<name>
actioncheck = <actioncmd> -n -L <chain> | grep -q fail2ban-<name>
actionban = <actioncmd> -I fail2ban-<name> 1 -s <ip> -j DROP
actionunban = <actioncmd> -D fail2ban-<name> -s <ip> -j DROP
[Init]
name = default
port = ssh
protocol = tcp
chain = INPUT
actioncmd/ipv = [(4, "iptables"), (6, "ip6tables")]
TEST[asdf] = 1
/etc/fail2ban/fail2ban.conf changed:
[Definition]
loglevel = 4
logtarget = /var/log/fail2ban.log
socket = /var/run/fail2ban/fail2ban.sock
/etc/fail2ban/filter.d/dovecot.conf [Errno 13] Permission denied:
u'/etc/fail2ban/filter.d/dovecot.conf'
-- no debconf information
--- End Message ---
--- Begin Message ---
awesome! so it works -- bouncing of the email with bug is enough! Though
my mutt refuses to use [email protected] for reply, although
Reply-To is set... weird
On Tue, 12 Jul 2011, Yaroslav Halchenko wrote:
> Package: fail2ban
> Version: 0.8.4-3.1~bugstry0
> Severity: normal
> ok -- testing! please disregard if you manage dto receive it
--
=------------------------------------------------------------------=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
--- End Message ---
