The Problem
Your
application needs to be capable of sending email, but you have
no control over where your application is deployed. Your end-user
might be running the application on a computer that is behind
a firewall that blocks access to SMTP servers outside of it.
In this case, you are only able to send email using an SMTP
server inside the firewall, if there is one, and if that server
requires authentication, your application would be incapable
of sending email altogether. What you really need is the ability
to send email from your own SMTP server from anywhere, regardless
of firewalls. Chilkat Mail provides a solution.
First
some background on why outbound port 25 (SMTP) traffic is sometimes
blocked. Some ISPs block outbound traffic to port 25 in an attempt
to prevent spam or unsolicited commercial email (junk email).
They are worried about being held liable for their subscribers
causing damage to other computer networks by using outside SMTP
servers for spamming.
The Solution
Chilkat
provides an executable (ChilkatCGI.exe) that you can place on
your Web server in the cgi-bin directory. We also provide a
new method "SendCGI". This method will encode your
email, which can contain anything, including attachments, and
send it via an HTTP POST to the ChilkatCGI.exe. The encoded
message includes your SMTP server hostname and authentication
information in AES encrypted form so that the CGI can unpackage
the message and send email from within your firewall. This solution
depends on the HTTP POST (port 80) being able to succeed from
the end-user's location. But that is much less likely to be
blocked as opposed to port 25. If a HTTP proxy exists, Chilkat
Mail will automatically use it.
The Download
ChilkatCGI.exe
(320KB)
