Bug#315656: exim4-config: Split config files with names containing full stops silently ignored

[Andreas Metzler]

On 2005-06-24 Ewan Mellor <debian-bug@ewanmellor.org.uk> wrote:
> Package: exim4-config
> Version: 4.50-8
> Severity: normal

> I created a file named

> /etc/exim4/conf.d/rewrite/20_exim4-config_rewrite-example.com

> expecting the configuration to be picked up by update-exim4.conf.  However,
> this file was silently ignored.  update-exim4.conf performs sanitisation 
> inside run-parts:
[...]
> This ignores any files not matching [[:alnum:]_-]+.

> I presume the check is there for a good reason, but it is certainly too
> strict.  Having full stops in filenames is not unusual!

Hello,
this behavior intentionally mirrors the behavior of run-parts(1) and
afaict is not going to change. run-parts(1) is used widely in Debian
and the paradigma that "mv foo foo.something" disables reading the
file is quite common.

We are probably going to switch to using "run-parts --list" once we
decide to no care for backports on woody.

> Secondly, no warning was issued when this file was ignored.  There is 
> even an option to update-exim4.conf:

>        -v|--verbose - Enable verbose mode, tell about ignored files

> but even with this option on, the ignored file was not mentioned.
[...]

The documention is not up to date in this respect. Thank you for the
note.
                 cu andreas
-- 
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
                                           http://downhill.aus.cc/