Ok. The problem you had with File::Find (which I personally would feel more comfortable with, ive never even heard of File::Recurse) is that you didnt use the option no_chdir and/or you didn't use $File::Find::name. (Actually I have serious reservations about using a module that isnt in the standard distro when there is one in the standard distro that does the same thing. Theres good reason why it got into the standard distro in the first place.)

use strict;
use warnings;
use File::Find;

# Extensions to match
my @exts=qw(.nsf .exe); 
my $search_root='D:\\Bin\\'; # where to start the search

# Build a regex
my $rexstr=join'|',map {quotemeta $_} @exts; 
my $rex=qr/(?:$rexstr)$/i;

# list of filespecs
my @list;
# Find em thanks
find({ wanted =>sub{push @list,$_ if (/$rex/ && -f)} , no_chdir => 1 }
+, $search_root);
# And print em out
print join "\n",@list;
[download]

Adding the email code and etc is left as an exercise for the read... ;-)

BTW: Ive found there is a cute little trick with File::Find under windows. If you use MS style paths (ie backslashes) and dont take advantage of perls ability to handle either then File find will return paths like

D:\Bin\/autoruns.exe
[download]

Which means that you can easily tell where the childrens path starts by looking for slashes and not backslashes. (Dont worry about \/ Perl handles it transparently.) But be aware that using the trick makes your code completely unportable.

HTH

Yves / DeMerphq
--
When to use Prototypes?
Advanced Sorting - GRT - Guttman Rosler Transform