there are some examples around, where people modified an admin module for non-admin use, but be aware, that the core admin modules are currently designed for admin use and might not provide proper security settings, when used outside admin/host menu.

I just found on the web from Brian Orrel's blog: http://blogs.parivedasolutions.com/borrell/archive/2005/09/25/DNNBulkEmail.aspx 

I've always wanted to be able to allow end-users the ability to use the DotNetNuke Bulk-Email functionality without giving them full admin access to the site.

Even if the DotNetNuke Gods did not want to provide that functionality, I figured it couldn't be that difficult to get to work.  Sure enough, it wasn't.

First, I went into Module Definitions and created a new Module and Module Definition -- I called mine “Pariveda Newsletters” but you could call it whatever you want.  I then added a View control to the Module.  It doesn't matter what control you pick because you will be manually changing it later.

Then I ran the following SQL update statement to point my new module to the “Admin” Bulk Email control.

UPDATE ModuleControls
SET ControlSrc = 'Admin/Users/BulkEmail.ascx'
FROM ModuleControls MC
JOIN ModuleDefinitions MD on (MC.ModuleDefID = MD.ModuleDefID)
JOIN DesktopModules DM on (MD.DesktopModuleId = DM.DesktopModuleId)
WHERE DM.FriendlyName = 'Pariveda Newsletters'

Now you can place the “Pariveda Newsletters” control anywhere you darn well please and set security appropriately.  It's up to you.