Milter-greylist

I've been running milter-greylist for several months now and haven't really 
had any problems, however an issue came up a few days ago. It seems that 
milter-greylist is doing case sensitive checks on the recipient portion of an 
email address when checking whether the email needs to be greylisted or not. I 
did see in the changelog for version 1.3.1 that the autowhitelist was using 
insensitive checks, but that doesn't seem to be the case from what I'm seeing 
with version 4.0 (was running 4.0b1, but upgraded to 4.0 release, problem 
persisted).

Perhaps I'm doing something wrong, but for testing purposes I manually 
greylisted one of my machines in the conf file (local networks whitelisted 
below that in the conf), greylist period is 8m. After doing a few manual tests 
via telnet, here is what resulted in the greylist db (after sending a kill for 
it to dump the db):

208.29.27.25    <wtfover@...>      <ryan.moore@...> 
1204229260 # 2008-02-28 15:07:40

208.29.27.25    <wtfover@...>      <RYAN.MOORE@...> 
1204230627 # 2008-02-28 15:30:27

208.29.27.25    <wtfover@...>      <Ryan.Moore@...> 
1204230977 # 2008-02-28 15:36:17

Compile parameters were:
./configure --with-db --with-libspf2 --with-libmilter --with-pthread 
--with-thread-safe-resolver --with-user=smmsp


I saw an old thread from the archives, and the issue arose when a client of 
ours had some mail 'blocked' from one of their clients, I say blocked because 
the sending server never retried the emails (probably a brain-dead exchange 
box). The client sent to the same address, but with different cases (xyz@..., 
XYZ@...), with several hours between emails which should have been passed (was 
over the greylist period, but much less than the timeout).

If anyone has any advice, I'd greatly appreciate it, Thanks.

-- 

Ryan Moore
----------
Perigee.net Corporation
704-849-8355 (sales)
704-849-8017 (tech)
www.perigee.net