3Pay SIM on APN three.co.uk. Has anyone any experience with them blocking
some ports? It appears SMTPS (I think that's port 465) is being blocked -
but I'm trying to diagnose this over the telephone so am not sure what's
going on. Are they trying to force you into using 3Mail?

Do they block other ports? I thought they were fairly lax, but port 24
didn't seem to work either.

Thanks
Theo

"Theo Markettos" wrote in message
...

3Pay SIM on APN three.co.uk. Has anyone any experience with them blocking
some ports? It appears SMTPS (I think that's port 465) is being blocked -
but I'm trying to diagnose this over the telephone so am not sure what's
going on. Are they trying to force you into using 3Mail?

Do they block other ports? I thought they were fairly lax, but port 24
didn't seem to work either.

Thanks
Theo


Normal SMTP port is 25, and i think it is blocked / charged for

I use SSL port 465 on googlemail

also change your APN to 3internet

Steve Terry
--
Get a free Three 3pay Sim with £2 bonus after £10 top up
http://freeagent.three.co.uk/stand/view/id/5276

Theo Markettos wrote:


3Pay SIM on APN three.co.uk. Has anyone any experience with them blocking
some ports? It appears SMTPS (I think that's port 465) is being blocked -
but I'm trying to diagnose this over the telephone so am not sure what's
going on. Are they trying to force you into using 3Mail?

Do they block other ports? I thought they were fairly lax, but port 24
didn't seem to work either.

Thanks
Theo

A google search for SMTPS turned up the following at
http://de.wikipedia.org/wiki/SMTPS (Google translation from German):

Originally, the Internet Assigned Numbers Authority in early 1997 to port
465 had registered for SMTPS. [1] This was withdrawn in late 1998, specified
as a STARTTLS was. [2] With STARTTLS same port can be used without TLS, and
TLS. [4] [5] For the SMTP was seen as particularly important because clients
respond with this protocol also foreign server from which they can not know
whether it is providing a separate port for TLS. [3] The port 465 is now
Source Specific Multicast for audio and video recorded. [4] [5]

[6] SMTPS will still remain available on port 465, but also on port 587 for
message submission to RFC 4409. [6]

At a guess, its the multicast service they want to block and you might
succeed with port 587 though that would depend on the server you're wanting
to connect to.

Good luck.

--
Steve Hayes, South Wales, UK
----Remove colours from reply address----

Steve Hayes wrote:
http://de.wikipedia.org/wiki/SMTPS (Google translation from German):

Originally, the Internet Assigned Numbers Authority in early 1997 to port
465 had registered for SMTPS. [1] This was withdrawn in late 1998,
specified as a STARTTLS was. [2] With STARTTLS same port can be used
without TLS, and TLS. [4] [5] For the SMTP was seen as particularly
important because clients respond with this protocol also foreign server
from which they can not know whether it is providing a separate port for
TLS. [3] The port 465 is now Source Specific Multicast for audio and video
recorded. [4] [5]

Funnily enough, that's what I eyeballed looking for port numbers but didn't
bother reading the German ;-)

It looks like my SMTP server is listening on 25, on which it sends an SMTP
greeting, and 465, to which the socket opens but nothing comes back when I
type in garbage, but nothing listening on 587. So the client must be using
25 (I can only see by asking someone to read out the config over the phone).

I can ask the server people to change the port to 26, so I'll give that a
try. Or maybe that's blocked too like 24? When I changed the daemon
listening on 24 to 443 (a good port for raw tunnels) it connected, so they
may be firewalling other 2x ports too.

Theo

In an earlier contribution to this discussion, Theo Markettos
wrote:
Steve Hayes wrote:
http://de.wikipedia.org/wiki/SMTPS (Google translation from German):

Originally, the Internet Assigned Numbers Authority in early 1997 to
port 465 had registered for SMTPS. [1] This was withdrawn in late
1998, specified as a STARTTLS was. [2] With STARTTLS same port can
be used without TLS, and TLS. [4] [5] For the SMTP was seen as
particularly important because clients respond with this protocol
also foreign server from which they can not know whether it is
providing a separate port for TLS. [3] The port 465 is now Source
Specific Multicast for audio and video recorded. [4] [5]

Funnily enough, that's what I eyeballed looking for port numbers but
didn't bother reading the German ;-)

It looks like my SMTP server is listening on 25, on which it sends an
SMTP greeting, and 465, to which the socket opens but nothing comes
back when I type in garbage, but nothing listening on 587. So the
client must be using 25 (I can only see by asking someone to read out
the config over the phone).

I can ask the server people to change the port to 26, so I'll give
that a try. Or maybe that's blocked too like 24? When I changed the
daemon listening on 24 to 443 (a good port for raw tunnels) it
connected, so they may be firewalling other 2x ports too.

Theo

There's some stuff about blocked ports on 3's site. Go to
http://www.three.co.uk/Help_Support/...Broadband_Help and type 'email'
in the search box - and follow the links about Port 25 etc.
--
Cheers,
Roger