Import ezmlm-idx 0.40
[ezmlm] / DOWNGRADE.idx
CommitLineData
f8beb284
MW
1$Id: DOWNGRADE.idx,v 1.3 1997/12/30 21:30:56 lindberg Exp $
2$Name: ezmlm-idx-040 $
3
4MODIFYING ezmlm-idx lists to work with "virgin" ezmlm-0.53
5
6With ezmlm-idx-0.22, the routines issub.c and subscribe.c are modified to
7store subscriber addresses using a hash based on the lower case address,
8rather than a case sensitive hash. This was done to avoid the many problems
9with subscribers using mixed case addresses (User@host and user@host) without
10realizing that these are different.
11
12These changes have no impact on lower case-only addresses. For mixed case
13addresses, the case in the local part is retained. If not found, a second
14lookup is done with a hash based on the mixed case address. This results in
15backwards compatibility with ezmlm-0.53 subscriber list.
16
17In the unlikely event that you use ezmlm-idx and then decide to go back to
18ezmlm-0.53 alone, mixed case addresses stored in the new location
19(case-insensitive hash) will not be found by the old ezmlm-0.53 programs.
20To place them in the ezmlm-0.53 position, do the following with your lists
21after installing the "virgin" ezmlm-0.53 binaries and backing up everything
22under DIR/subscribers:
23
24 % ezmlm-list DIR >tmp.tmp
25 % rm -rf DIR/subscribers/*
26 % xargs ezmlm-sub DIR <tmp.tmp
27
28This just recreates the subscriber database with the old style hash.
29
30This procedure can also be used to recover corrupted subscriber databases,
31by editing tmp.tmp before resubscribing.
32
33You can also identify the addresses that would be affected by:
34
35 % ezmlm-list | grep -G '[A-Z]'
36