11g utl_smtp Security

Question

I have an application which supports 'phoning home' that, up until 11g was relatively easy to implement. Now I'm attempting to port it so that it will work with 11g but unfortunately, this doesn't seem to be all that easy.
If I run this code as a scripted anonymous PL/SQL block it works:
dbms_network_acl_admin.add_privilege (
acl           => 'utlpkg.xml',
principal      => 'USERNAME',
is_grant      => TRUE,
privilege      => 'connect',
start_date      => null,
end_date      => null);
(Obviously, I've already created the acl in question). Unfortunately, if I attempt to run this from my administration application, or even try to put it in a stored procedure where I can just call it from my stored procedure, it does not work. I can't get it to compile in a stored procedure, and just running the SQL from my application raises no exceptions, but has no effect either. It appears that it must be commited in order for it to work, is this true? (In other words, unlike other Oracle security-related operations, this is not considered DDL?) Forcing a commit from my application has no effect, it still doesn't work.
I'd like to incorporate this level of security into my application as opposed to having to run it externally from a script in order for it to function. Clearly I'm missing something here, but my results seem arbitrarily inconsistent. This may be in part because of the general suckiness of Vista on which I'm running 11g, or perhaps a problem with 11g itself, or, most likely, my own inability to code it correctly. I would appreciate any pointers to existing code that I might incorporate.
Thanks!
<RANT> I have NO IDEA why Oracle would chose to implement security based on xml when there is an existing structure that's been in the database for as long as I've work with it (grant priv to user). This seems to me to be an abuse of what xml should be used for, and I can only hope this over-exuberant use of xml can be rectified in a future release </RANT>

Answer 1

Hi,
You have to many explanation here www.ietf.org/rfc/rfc0821.txt
and here
www.ietf.org/rfc/rfc0822.txt
Nicolas.