Ian Eiloart
2005-08-02 11:16:22 UTC
--On 2 August 2005 10:02:42 +0100 Ian Eiloart <***@SUSSEX.AC.UK> wrote:
>
> 4. Consider accepting connections ONLY from campus machines. That would
> mean people could not use the native client from home, but they could use
> the web client. You could let people register IP addresses - but that
> would only be useful for people with fixed IP broadband connections.
Oh, but many people won't be able to connect to the server on port 25
anyway. Presumably you're going to offer authenticated SMTP on port 587 in
order to allow people to bypass interception or blocking of port 25?
Anyway, Meeting Maker client can't be persuaded to use any port other than
25 for email, so some home users already can't use the email functions.
--
Ian Eiloart
Servers Team
Sussex University ITS
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>
> 4. Consider accepting connections ONLY from campus machines. That would
> mean people could not use the native client from home, but they could use
> the web client. You could let people register IP addresses - but that
> would only be useful for people with fixed IP broadband connections.
Oh, but many people won't be able to connect to the server on port 25
anyway. Presumably you're going to offer authenticated SMTP on port 587 in
order to allow people to bypass interception or blocking of port 25?
Anyway, Meeting Maker client can't be persuaded to use any port other than
25 for email, so some home users already can't use the email functions.
--
Ian Eiloart
Servers Team
Sussex University ITS
* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML