Like many places with a lively and long email history, we generate a number of different sorts ofoutgoing email. These sorts of email have different characteristics andthus different chances of being seen as spam email or bulk email by outside places .

So here's a rough list of the different sorts of email that our systemwinds up sending out:

• direct email from users; the least likely to be considered spam,since the users are typing it themselves.

• users forwarding email to outside places; oftenwinds up forwarding spam

Certain websites and I have a disagreementof opinion. To wit, they feel that my account is vitally important,so important that they must save me from myself by refusing to let mybrowser remember the password for me. I disagree with them, becauseultimately they are just another website. Sure, it would be annoying ifan attacker deleted my account or the like, but in the global scale ofthings it is not that big a deal.

(I will excuse people being paranoid if they are holding my money

One of the things that security people always say is that the first stepin doing a decent security analysis is to figure out your threat model . So, what is the threatmodel for website logins, in other words what sort of attacks are youlikely to face that you need to defend against?

My belief is that there are two or maybe three significant threats thesedays:

• phishing, for which the best defense is getting your users out of thehabit of entering their passwords at all; either have them logged on

I wrote up our basic fileserver design plan back in ZFSFileserverDesign , but it is worth explaining why we are lookingat using many pools. In a nutshell:

Given that we sell fixed size chunks of space to people (as the waywe allocate our storage space), we are always going to have a certainnumber of logical pools of storage to manage. The only question iswhether to handle them as separate ZFS pools or to aggregate them intofewer ZFS pools and then administer them as sub-hierarchies using quotas .