Warn if config file present but unreadable
Fix up for warning/error for inaccessible config files
Update config/jail.conf

Update to use the new sogo-auth filter
Create sogo-auth.conf

Regexp works with SOGo 2.0.5 or newer, following new feature implemented here: http://www.sogo.nu/bugs/view.php?id=2229
Update config/filter.d/sogo-auth.conf

Comment line in the top altered to fit file name. My local file was named differently...
NF: allow customization configuration under corresponding .d directories (Closes gh-114)

Additional changes:
  ENH: make basedir for Config's a kwarg to the constructor
  ENH: improved analysis/reporting on presence/accessibility of config
       files.  Got carried away and forgot about existing  work done by
	   Steven Hiscocks in the gh-115 -- will merge it in the next
       commit for the fair ack of his work

Now for any X.conf configuration file we have following ways to
provide customizations

  X.local -- read after .conf (kept for backward compatibility)
  X.d/ -- directory to contain additional .conf files, sorted
               alphabetically, e.g
  X.d/01_enable.conf       - to enable the jail
  X.d/02_custom_port.conf  - to change the port

X could be a 'jail' or 'fail2ban' or any other configuration file in
fail2ban.

Mention that all files still must contain the corresponding sections
(most of the time duplicating it across all of them).
Merge remote-tracking branch 'github_kwirk_fail2ban/upstream#24' into _tent/conf_d

Merge is done with -X ours -- since I have implemented more generic handling
for config files, including now the ones under .d/ subdirectories.

* github_kwirk_fail2ban/upstream#24:
  Fix up for warning/error for inaccessible config files
  Warn if config file present but unreadable
ENH: made log messages while parsing files more informative + test for inaccessible file (Closes: gh-24)
Reincarnated removed (by mistake) test for SplitAction
Downgrade log rotation detection message to DEBUG level from INFO. Closes: gh-129

This message useful only when debugging problems so it is more reasonable
to have it suppressed otherwise
invalid date recognition, irregular because of sorting template list (sometimes not reproducible by fail2ban-regex, cause will be not sorted)

date in following log line (from nginx) will be wrong detected:
2012/10/11 02:37:17 [error] 18434#0: *947 user "test" was not found in "/www/...", client: 192.168.1.5, ...

sometimes it is [correct] - 2012/10/11 (%Y/%m/%d) = 1349919861.71
sometimes it is [invalid] -   12/10/11 (%d/%m/%y) = 1349915838.06
and older as now - 1800 seconds (therefore will be not found)

solution: regular expression fixed, cause date in log used always after non symbol (\W) character, so r"\d{2}/\d{2}/\d{2}" will be r"(?<!\w)\d{2}/\d{2}/\d{2}".
refresh generated manpages (since 0.8.2 state)
FSF address changes missing from previous
Add development documentation and framework for code coverage measurement
BF: general Exception catch was excessive. Only IOError and OSError are possible and has different meanings
BF: allow more than single word for command action[start,stop,ban,unban,check] and for setcinfo too
ENH: add help command
ENH: typo + head -1 has been deprecated for 10+ years.
Merge pull request #133 from grooverdan/development-code-coverage

coverage pragma comments, improved documentation for the developers
do catch all exception