This is implementation of Oracle's API of packages utl_mail, DBMS_MAIL

It doesn't ensure full compatibility, but should to decrease a work necessary for successful migration.

These functions can be used by user that is member of role orafce_mail. For setting of orafce_mail.smtp_server_url the user should be member of role orafce_mail_config_url. For setting of orafce_mail.smtp_server_userpwd the user should be member of role orafce_mail_config_userpwd.

set orafce_mail.smtp_server_url to 'smtps://smtp.gmail.com:465';
set orafce_mail.smtp_server_userpwd to '[email protected]:yourgoogleapppassword';

call utl_mail.send(sender => '[email protected]',
                   recipients => '[email protected]',
                   subject => 'ahoj, nazdar, žlutý kůň',
                   message => e'test, \nžlutý kůň');

do $$
declare
  myimage bytea = (select img from foo limit 1);
begin
  call utl_mail.send_attach_raw(sender => '[email protected]',
                                recipients => '[email protected]',
                                subject => 'mail with picture',
                                message => 'I am sending some picture',
                                attachment => myimage,
                                att_mime_type => 'image/png',
                                att_filename => 'screenshot.png');
end
$$;

This extensions uses curl library.

An extension Orafce should be installed before

Sending to remote smtp server is pretty slow. This is not an issue of orafce_mail or curl library. So don't try to send mails from performance critical processes. Use some buffer table, and send mails from another process started by cron or some scheduler application, or use local smtp server. Postgres has great LISTEN/NOTIFY mechanism.