28 Oct
2011
28 Oct
'11
8:30 a.m.
On 28/10/11 09:29, Joseph Heenan wrote:
On 27/10/2011 21:16, Andy Smith wrote:
Which got me thinking that t-mobile must be *monitoring* or even
*proxying* the connection and chopping it off once it threatens
to become encrypted and unmonitorable.
With that in mind a bit of googling led to:
http://support.t-mobile.co.uk/help-and-support/index?page=support&cat=M…
which I think explains it.
So you're saying that you have a device on t-mobile and you're trying
to reach a bitfolk IP address on port 587 and it doesn't work?
Correct -
though it doesn't work in a very particular way:
The SMTP connect opens fine, client says EHLO, server responds, client
says STARTTLS, server responds successful - then the server receives a
TCP RST.