Hi Craig. I'm not to versed in your specific topic, but what I have done to
get past security for other things is piggyback allowed protocols to an
outside server that can then serve as a proxy and do the task you require
without all the restrictions.
Example. I have this Jegas Application Server product I've been working on
for years. It's now a standalone webserver with extras to make it worth it.
But, I have an application that simply REQUIRES Apache. Great. BUT - the
catch is I need AJAX services from the JAS server while "living in" the
APACHE Server. Browsers have cross site restrictions for AJAX but my reasons
for doing so are legit. So what I did was, I created a CGI application that
is rather "lightweight" that gets "the AJAX" request parameters etc via
apache's CGI interface (it fires up when called, collects the ajax request
parameters) the request is sent via TCP to JAS web server (different ports
etc), it processes the request, and sends it back to the CGI app, which in
turn sends it back to apache - and it's all pretty much instantaneous.
Now, I know what you're doing is different. However I wonder how hard it
would be turn that email into a SSL web page request out to the internet
where your "special server" is waiting for such a request, gets it, and
performs the sendmail off site?
--Jason
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
