That wouldn't help either, since all receiving email servers would have to
be listening on the non-standard port as well. Remember that this is for
server to server communication, not client to server. In the case being
discussed, the originating client and the server are (would be) on the same
machine. The problem comes in when the originating email server tried to
make the connection to the destination domain's server. If the ISP is
blocking port 25, the connection won't happen.
On 9/1/01 2:15 AM, "Timothy Bates" <[EMAIL PROTECTED]> wrote:
> you could set the mailer to point to a non-standard (unblocked) port
>
> On 9/1/01 6:59 AM, "Diane L. Schirf" <[EMAIL PROTECTED]> wrote:
>> On 8/31/01 10:21, Steve Sell at [EMAIL PROTECTED] wrote:
>>
>>> What CAN happen is that your ISP can set all of their routers to
>>> block any traffic that is destined for ANY port 25 unless the traffic
>>> originates on their mail server.
>>>
>>> This effectively says that only mail to or from one of their servers can be
>>> sent.
>>>
>>> Even though your sendmail would accept the mail from your client, it would
>>> need to make a connection to port 25 on the destination computer to deliver
>>> the mail. If your ISP is blocking all TCP/IP packets desitined for port 25
>>> (unless it's theirs), that connection will not happen.
>>
>> This is exactly what Earthlink/Mindspring does -- blocks port 25.
>
> Dr Timothy Bates <mailto:[EMAIL PROTECTED]>
> Macquarie Centre for Cognitive Science (MACCS)
> Macquarie University
> Ph 61 (2) 9850 8623
> Fx 61 (2) 9850 6059
>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
