chuckee wrote:
>
>
> Dave Evans-14 wrote:
>> On Mon, Jan 14, 2008 at 02:09:46AM -0800, chuckee wrote:
>>> The users are actually paying for the SMTP server - it is the only reason
>>> they are using the server in the first place. It is a paid SMTP service
>>> that
>>> I am offering.
>> Fine, and SMTP is defined to run on port 25. The related Submission
>> protocol
>> runs on port 587. So if they are paying you for an SMTP service, you
>> provide
>> that service on port 25 and 587.
>>
>> If some combination of installing webmail on your system (thereby making
>> your
>> mail service accessible over port 80 - albeit using HTTP, not SMTP) and
>> offering SMTP (port 25) and Submission (port 587) still doesn't satisfy
>> your
>> users, then your users need to get non-crippled 'net connections, or more
>> realistic expectations.
>>
>
> Sadly, only having two port open on 25 and 587 would mean that a great
> percentage of users would not be able to access the server. In fact, port 80
> is often the only port open in places such as hotels and airports. They are
> paying me to offer the non-standard service, as the standard services out
> there do not work for them.
In my experience, such setups normally don't just leave port 80 open and
block the rest, they block everything and then run a transparent proxy
to reduce bandwidth usage and to help with policing access. That type of
setup would not work with what you are trying to do.
I used to install wireless internet access in hotels, motels and the
like and that is exactly how I had it setup. Any unknown client was sent
to an instructions page on how to use the service. If anyone had
attempted to talk SMTP through this setup they would have received a
"request error" and be sent back the troubleshooting guide.
--
The Exim Manual
http://www.exim.org/docs.html
http://www.exim.org/exim-html-current/doc/html/spec_html/index.html
