Package: postgrey
Version: 1.24-1
Severity: normal
Tags: patch
When the new --privacy option is added to POSTGREY_OPTS in
/etc/default/postgrey, the daemon can not start :
# /etc/init.d/postgrey restart
Restarting postfix greylisting daemon: postgreyCan't locate Digest::SHA1 in @INC
(@INC contains: /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8
/usr/local/lib/site_perl) at /usr/sbin/postgrey line 478.
(zsh: exit 2 sudo /etc/init.d/postgrey restart)
Please note I have libdigest-sha1-perl installed, which means this Perl module
is in /usr/lib/perl5/Digest/SHA1.pm. This problem occurs with 1.24-1, either on
Sarge or on Sid.
The following patch solves this problem; I mean, the daemon starts without any
error message - I've not checked if the personnal data is actually stored in a
hashed way, as supposed with the --privacy option:
--- orig/postgrey-1.24/postgrey 2006-02-05 13:52:05.000000000 -0800
+++ postgrey-1.24/postgrey 2006-02-05 13:52:19.000000000 -0800
@@ -474,7 +474,7 @@
# --privacy requires Digest::SHA1
if($opt{'privacy'}) {
- require 'Digest::SHA1';
+ use Digest::SHA1 qw(sha1_hex);
}
$0 = join(' ', @{$server->{server}{commandline}});
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.15-20060203
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to fr_FR.UTF-8)
Versions of packages postgrey depends on:
ii adduser 3.63 Add and remove users and groups
ii libberkeleydb-perl 0.26-3 use Berkeley DB 4 databases from P
ii libnet-dns-perl 0.48-1 Perform DNS queries from a Perl sc
ii libnet-server-perl 0.87-3 An extensible, general perl server
ii perl 5.8.4-8sarge3 Larry Wall's Practical Extraction
ii ucf 1.17 Update Configuration File: preserv
-- debconf information:
postgrey/1.13-5_move-db:
postgrey/1.14-1_lookup-by-subnet:
postgrey/1.13-5_old-config:
--
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
