Bug#600272: fail2ban: must add charset header on all notifications

2012-01-11 Thread Teodor MICU
2012/1/11 Yaroslav Halchenko : > would you be so kind to test with 1 more patch in that branch which > removes (which should be) bogus left-over ContentType var definition I initially tested like this and it didn't worked as expected -- POSIX instead of en_US.UTF-8. No idea why. > to resolve the

Bug#600272: fail2ban: must add charset header on all notifications

2012-01-11 Thread Yaroslav Halchenko
On Wed, 11 Jan 2012, Teodor MICU wrote: > > Could you check if something like that is working for you? > > https://github.com/yarikoptic/fail2ban/commit/ed9000c469b4554aab3e9b5365b959520096f3ba > I've tested that patch and it works, meaning it adds Content-Type: > header. This was tested against f

Bug#600272: fail2ban: must add charset header on all notifications

2012-01-11 Thread Teodor MICU
2012/1/10 Yaroslav Halchenko : > Could you check if something like that is working for you? > https://github.com/yarikoptic/fail2ban/commit/ed9000c469b4554aab3e9b5365b959520096f3ba I've tested that patch and it works, meaning it adds Content-Type: header. This was tested against f2b from Debian 6.

Bug#600272: fail2ban: must add charset header on all notifications

2012-01-10 Thread Yaroslav Halchenko
only with your help! ;) Could you check if something like that is working for you? https://github.com/yarikoptic/fail2ban/commit/ed9000c469b4554aab3e9b5365b959520096f3ba On Fri, 06 Jan 2012, Teodor MICU wrote: > > should be set to LC_CTYPE locale (or recoded once again?) which > > seems to be use

Bug#600272: fail2ban: must add charset header on all notifications

2012-01-05 Thread Teodor MICU
Hi, 2010/10/15 Yaroslav Halchenko : > should be set to LC_CTYPE locale (or recoded once again?) which > seems to be used by whois while converting from server-native (if known) > charset.  I will get it fixed when I get a moment Ping? Any chance to have this fixed for Debian 7.0? Thanks -- To

Bug#600272: fail2ban: must add charset header on all notifications

2010-10-15 Thread Yaroslav Halchenko
severity 600272 normal thanks should be set to LC_CTYPE locale (or recoded once again?) which seems to be used by whois while converting from server-native (if known) charset. I will get it fixed when I get a moment P.S. please in the future do not raise severity above normal unless there i

Bug#600272: fail2ban: must add charset header on all notifications

2010-10-15 Thread Teodor
Package: fail2ban Version: 0.8.3-2sid1 Severity: important Hi, Some whois queries are returning data in UTF-8 and are not displayed properly by the email client because it is missing this header: Content-Type: text/plain; charset=UTF-8 Please add this header to at least messages that contain D