Yes, that is how I understand it to work With the addition that having access to the mail profile
isn't enough. You also need to be a member of the  DatabaseMailUserRole (for which you need a user
in msdb).

Ok, I figured out how to create a private profile, looks like you need to add users to the
DatabaseMailUserRole in msdb to create a private profile.  I've now got this working.  However, both
of these accounts are sysadmins on the box I am testing on.  Why do you still need to add a sysadmin
to this msdb role?  I would assume something like that is granted by default to sysadmins, but I
guess I know what happens when I assume... .

So can someone please answer my questions below in red?

Thanks,
Rubens
 "Rubens" <rubensrose@hotmail.com> wrote in message news:O0v0cV5hIHA.536@TK2MSFTNGP06.phx.gbl...
 I am trying to create a Private Profile for Database Mail, however there are no accounts available
for me to select.  I can and have successfully sent mail from a public profile containing 2
different accounts, so I know I have it working.

 How can I create a private profile?

 Also, I want to confirm I understand the difference between the two options.  A public profile
allows mail to be sent by any account in any SQL instance that might be installed, correct?  Also
from what I understand, a private profile allows you to restrict which accounts have access to send
from a particular database mail profile, correct?

 Thank-you,
 Rubens