Ian Eiloart wrote:
>
>
>
> --On 13 January 2008 15:40:17 -0800 chuckee <mi6@???> wrote:
>
>>
>> Hi,
>> I was wondering how to do this:
>> I want to have Exim open on port 80 on my server (say, myserver.com),
>> however I also have a website that needs to be visible (on port 80), at
>> least on www.myserver.com and also myserver.com if possible.
>>
>> I need Exim open on port 80 because many of my users are accessing Exim
>> from networks where port 80 is the only port that is open (e.g.
>> airports).
>
> Port 587 is the official alternate port for *authenticated* smtp. Sites
> that permit Internet access ought to have this port open. Sites that
> provide email ought to provide authenticated SMTP (only) on this port.
> Email clients ought to use port 587 by default (the iPhone does, for
> example).
>
> There are some tips on configuring Exim for MSA here:
> <http://www.exim-users.org/forums/showthread.php?t=831>
>
> If you *really* need to provide port 80, then you can use the same tips.
> However, I'd hate to see this catch on. Please deploy port 587 first, and
> ask your users to try port 587.
>
>
Port 587 is for *authenticated* SMTP, as you say. My SMTP uses a different
'quota' system where users don't authenticate, but rather are restricted to
a lowish number of emails per day (and before you say 'open relay', this
system has been proven to be an effective alternative to authentication for
over 10 years). Spammers don't have the incentive to try to guess an actual
member's email address (exim looks at the sender's 'from' email address to
determine if they are allowed to send), and I have never seen anyone
successfully guess a member's email address yet. Trust me - it works, so
let's not discuss that strategy.
Because port 587 is for authenticated SMTP, I do not think I can or should
use it for this.
--
View this message in context:
http://www.nabble.com/How-to-have-port-80-open%2C-along-with-a-website--tp14792864p14818867.html
Sent from the Exim Users mailing list archive at Nabble.com.