You really need to think about everything you put into a database in terms of relationships (as mentioned by other posters). In the example you gave a user is going to have a one to many relationship with things like mail, they will have a one to one relationship with their user profile, and they will have a many to one relationship with something like 'locations' where many users live in one city.
As you are designing your database always ask yourself which relationship type you need to build and make an attempt to never duplicate data in multiple tables when you don't need to.
When you set up something like a users table make sure that every row is equal to a user (as opposed to every user being a table) and that every row has a unique auto-increment id. This user id (that is generated by MySQL) is going to be the reference that you use in other tables to link your data together.
So when you setup your mail table you might have 15 rows containing email data, but each of those rows will contain a field named something like user_id that will contain the unique id of that user from the users table.
Start getting familiar with things like LEFT JOIN--this is how you will run a single query and get, for example, your user's data AND all of his email at once.