Hi list, I'm building a proof-of-concept system using a unix box (freebsd) on an enterprise lan, the unix box hosts apps that send email to internal users. I had been using ssmtp to send mail via an internal open mail relay server, but now port 25 traffic is blocked to non-official systems by internal firewalls. The freebsd box isn't "official" which means it can't be given access, but it can't be official until the proof-of-concept works (classic catch-22). I don't know if port 465 (secure SMTP) is blocked.
I thought of two options: 1. if port 465 is not blocked, can ssmtp (or something else) be used to send secure SSMTP to an Exchange server using my personal network credentials? 2. instead of the unix box sending the mail, is anyone familiar with a Windows app I can run (on my Windows workstation) that will connect to the unix system, get queued outgoing mail, and then send the mail to the Exchange server as though it was coming from my Windows Outlook client? (I seem to recall something that ran on Win98 called "SoHo mail server", but will have to research later as our web firewall blocks all things networking). I'm not trying to subvert enterprise security; I think it's a good idea not to allow unsecured and unmanged systems free rein on an intranet. What I'm essentially proposing is to temporarily extend my personal credentials to include mail from the unix system. I will be responsibile for sent mail (and the mail is to internal users only), and when the proof-of-concept works, the project can go official - and then firewall rules and service accounts can be authorized. Does anyone have any suggestions or other thoughts? Dale -- www.dalescott.net Transparency with Trust _______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
