>>From an ISP point of view this makes perfect sense- but if you are a >>company > with only one userbase- this is really unhelpful. > > You have a supplier that deals with multiple members\teams of your > company- > you would have to whitelist for all of them. What happens if someone is > away > on holiday and sets up an OoO message to someone who is covering- that > supplier then wouldn't be whitelisted.
The other problem you run into is when you have different aliases for a user. For example John Smith @ domain.com could be john @domain.com, jsmith @domain.com, john.smith @domain.com, etc... Consequently, I think it would be very difficult to do on a per-user basis. However, I do agree that this can become problematic for those that are hosting multiple different domains, especially from different parts of the world. I could see a valid compromise as it having the whitelist working on a per-domain basis instead. Maybe have that as an admin option. Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
