Database Mail definition - confusing

Hello,
>From BOL:
For improved security, Database Mail manages access to mail profiles. A
profile may be public or private. Public profiles are available for all
members of the DatabaseMailUserRole database role in the msdb database.
They allow all members of the DatabaseMailUserRole role to send e-mail
using the profile.
To use a private profile, sysadmin must grant users permission to use
the profile. In addition, execute permission on the sp_send_dbmail
stored procedure is only granted to members of the
DatabaseMailUserRole. A system administrator must add the user to the
DatabaseMailUserRole database role in order for the user to send
e-mails.
What's confusing that that DatabaseMailUserRole is a PUBLIC role.
However, if you create a private profile, it says you must add the user
to the DatabaseMailUserRole in order for the user to send emails. That
would make the any member of this role a public profile?
I guess I am confused about the language here, so in effect I have no
clue what the end result of adding a user from a PRIVATE profile into a
role that is available for PUBLIC profiles.Hi
If I have interpreted your interpretation right, I think there is some
confusion between a role which is not a fixed database role, and the public
database role.
John
"tootsuite@.gmail.com" wrote:
> Hello,
> >From BOL:
> For improved security, Database Mail manages access to mail profiles. A
> profile may be public or private. Public profiles are available for all
> members of the DatabaseMailUserRole database role in the msdb database.
> They allow all members of the DatabaseMailUserRole role to send e-mail
> using the profile.
> To use a private profile, sysadmin must grant users permission to use
> the profile. In addition, execute permission on the sp_send_dbmail
> stored procedure is only granted to members of the
> DatabaseMailUserRole. A system administrator must add the user to the
> DatabaseMailUserRole database role in order for the user to send
> e-mails.
> What's confusing that that DatabaseMailUserRole is a PUBLIC role.
> However, if you create a private profile, it says you must add the user
> to the DatabaseMailUserRole in order for the user to send emails. That
> would make the any member of this role a public profile?
> I guess I am confused about the language here, so in effect I have no
> clue what the end result of adding a user from a PRIVATE profile into a
> role that is available for PUBLIC profiles.
>

Database Mail definition - confusing

Hello,

>From BOL:
For improved security, Database Mail manages access to mail profiles. A
profile may be public or private. Public profiles are available for all
members of the DatabaseMailUserRole database role in the msdb database.
They allow all members of the DatabaseMailUserRole role to send e-mail
using the profile.
To use a private profile, sysadmin must grant users permission to use
the profile. In addition, execute permission on the sp_send_dbmail
stored procedure is only granted to members of the
DatabaseMailUserRole. A system administrator must add the user to the
DatabaseMailUserRole database role in order for the user to send
e-mails.
What's confusing that that DatabaseMailUserRole is a PUBLIC role.
However, if you create a private profile, it says you must add the user
to the DatabaseMailUserRole in order for the user to send emails. That
would make the any member of this role a public profile?
I guess I am confused about the language here, so in effect I have no
clue what the end result of adding a user from a PRIVATE profile into a
role that is available for PUBLIC profiles.Hi
If I have interpreted your interpretation right, I think there is some
confusion between a role which is not a fixed database role, and the public
database role.
John
"tootsuite@.gmail.com" wrote:

> Hello,
>
> For improved security, Database Mail manages access to mail profiles. A
> profile may be public or private. Public profiles are available for all
> members of the DatabaseMailUserRole database role in the msdb database.
> They allow all members of the DatabaseMailUserRole role to send e-mail
> using the profile.
> To use a private profile, sysadmin must grant users permission to use
> the profile. In addition, execute permission on the sp_send_dbmail
> stored procedure is only granted to members of the
> DatabaseMailUserRole. A system administrator must add the user to the
> DatabaseMailUserRole database role in order for the user to send
> e-mails.
> What's confusing that that DatabaseMailUserRole is a PUBLIC role.
> However, if you create a private profile, it says you must add the user
> to the DatabaseMailUserRole in order for the user to send emails. That
> would make the any member of this role a public profile?
> I guess I am confused about the language here, so in effect I have no
> clue what the end result of adding a user from a PRIVATE profile into a
> role that is available for PUBLIC profiles.
>

Database Mail - Command not Supported error

Hi All,

I am trying to get Database mail running on SQL 2005. I have, very carefully, followed all the steps in BOL, and the Improved steps suggested in other posts on this forum (in particular
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=109885&SiteID=1
).

However when I try to send mail I get the error:

The mail could not be sent to the recipients because of the mail server failure.
(Sending Mail using Account 2 (2006-02-20T10:55:30).
Exception Message: Cannot send mails to mail server.
(Command not implemented. The server response was: Command not Supported).
)

Searching through other forums it appears that this is an SMTP issue of some sort:

(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=112971&SiteID=1)

Anyone else seen this?

Unfortunately I didn't set up the server, so there may be required Windows components missing. When I first saw the error and tried to go through the steps in link 1 above, I discovered that SMTP was not on the box(!). It is up and running now, but I wonder if there is anything else missing.

Thanks, as always,

Richard R.

Richard,

I'm moving your thread to the Tools General forum. Hopefully they'll be able to answer.