Comment 4 for bug 583379

I have committed the changes to the stable branch at lp:~systers-soc/systers/stable.

The functions that received lowercase email address (even though the email-id was stored in uppercase in database) are:

1)getSubscriber_id_raw(self, addr) : addr is in lowercase
2)getSubscriber_id_raw_or_die(self, addr) : addr is in lowercase
3)setDisable(self, member, flag) : member is in lowercase
4)setDigest(self, member, flag) : member is in lowercase
5)changePreference(self, member, preference) : member is in lowercase
6)changeFormat(self, member, format) : member is in lowercase
7)changeAddress(self, oldaddr, newaddr) : oldaddr is in lowercase but newaddr come out to be uppercase
8)unsubscribeFromList(self, key) : here email id is recieved in lowercase
9)subscribeToList(self, key) : here email id is recieved in uppercase
10)mergeSubscribers(self, oldaddr, newaddr) : oldaddr is in lowercase and newaddr is in uppercase

Again want to mention that when I write " 'x' is in lowercase " I mean that even though the mail id was stored as uppercase in database but the functions get lowercase email-id as their input parameter.

I have made the necessary changes to handle the above issues but was not able to test whether members with uppercase email-id are able to post easily,create new thread or continue existing ones or not as locally I need to create users on my ubuntu and I found that ubuntu does not allows us to create users with uppercase letters in it.So I leave this part of testing on the testing rounds we will be conducting.