Arnt Gulbrandsen wrote:
Hector Santos writes:
Excuse me if I am not following you, but the compares are
implementation specific. Like Finch pointed out, Sieve doesn't care.
Sieve suggests treating localparts case insensitively. Any user may
follow the suggestion or explicitly choose something different from the
default.
This is not specific to any implementation: Any conforming sieve
processor behaves this way.
So what you are saying is that if we implement Sieve, to be Sieve
compliant, our implementation must provide user preferences in regards
to case?
--
Sincerely
Hector Santos
http://www.santronics.com
