How difficult would it be to add a mailing list option like this:
IGNORECASE=(0|1)
Where '0' would be the default, so that mailing lists continue to behave like they do now, while '1' would allow posting and unsubscribing without regard to the case of the return address.
Is this a quick-n-easy job, or would it take some time?
Medium -- there are several places that need to be changed.
The only situation where this would be a problem is if they purposefully reconfigured their mail client to use a different case after subscribing, and I can't fathom why this would be the case.
Granted, not many people do this, but as the admin for ~250 lists and counting, the once-in-a-while occurrences are starting to add up. What usually happens is someone who is relatively new to email starts with an address like "[EMAIL PROTECTED]", and then after a few months decides that his emails will look better if his return address is "[EMAIL PROTECTED]".
But here's a second scenario, which is actually more common in my case: I don't acutally run the lists -- I'm just the guy who people call when there are problems. There are ~150 users who are in charge of 1-2 lists each; the setup is kind of like the sourceforge lists or the yahoo groups. A lot of the people using the lists are in bands, and they'll be out a gig or something where people will come up in person, give them their email address, and ask to be put on the mailing list. In order to accomodate this I've written a little wrapper to the 'couriermlm' command that allows the list maintainers to add people to the list manually. But since no-one is used to email being case-sensitive they don't say 'capital-B-lowercase-o-b-capital-S...'. So they get usually get subscribed with all lowercase letters, and then a few months later when they try to unsubsubscribe (people move, they're no longer interested in the band, the band talks too much, etc...), it causes tension because the unsubscription won't work.
Again, neither situation is common, and back when I only had to deal with a few dozen lists it was no big deal to handle the occasional complaint. But now it's getting to be a weekly issue. I poked around a little to see if this would be something I could patch on my own, but I don't have a lot experience with C/C++ and I'm not familiar with the courier code at all. Given an already tight schedule, it's just not feasable.
So, here's a proposition: Given that this would involve some non-trivial changes and it isn't of immediate concern to you personally, I'll offer some kind of payment if you can make the time for it. How much time are we talking here, and what would be a fair reward?
If there's no way you could make time for this anytime soon, please let me know and I'll offer a bounty to the others on the list in case someone else wants to give it a shot.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
