Phorm and Cookies

[Roland Perry]

In article <47F52DC4.7050403@zen.co.uk>, Peter Fairbrother 
<zenadsl6186@zen.co.uk> writes
>Roland Perry wrote:
>>
>> All the regulators I've ever spoken to would say "there is plenty of 
>>competition in the market, choose an ISP that doesn't block port 25".
>>  In any event, aren't there already ISPs that won't allow you to post 
>>emails "from" @jfirth.net, rather than "from" @isp-x.com, unless they 
>>are also hosting jfirth.net for you?
>
>There are, quite a few of them, and many others want you to register 
>with them if you want to send SMPT mail directly. In fact it is getting 
>to the stage where there _aren't_ plenty of ISPs who permit port 25 
>traffic.

ISPs are doing this as an anti-Spam measure I suppose. Life gets more 
difficult all the time. However, in terms of number-of-ISPs (rather than 
market share) I expect there still hundreds to choose from.

>Third-party email services will
>> handle your inbound jfirth.net email, of course, but not all of them 
>>offer an SMTP service to *send* it (and/or do so, but charge extra).
>
>Googlemail,Hotmail and other web-based email services will send SMPT 
>emails for free,

If I send them the email via port 25?

>and there are several independent mail servers (eg 1&1 run one) which 
>charge about £10 per annum.

That'll be the "charge extra".

>One question, when you send an email to a relaying mail server, perhaps 
>operated by your ISP, where the mail server is the SMTP client rather 
>than you, what port number does the communication between you and the 
>mail server use?

Port 25.
-- 
Roland Perry