28 Oct
2011
28 Oct
'11
7:29 a.m.
On 27/10/2011 21:16, Andy Smith wrote:
Hi Joseph,
On Thu, Oct 27, 2011 at 02:34:03PM +0100, Joseph Heenan wrote:
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.
Switch over to wifi and everything is fine.
I believe I already know the answer to this, but
can someone from bitfolk
please confirm that you don't block traffic from t-mobile 3G ip addresses
on port 587...?
The answer is no, not intentionally.
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? Does any form of connectivity work?
Yes, I've not found any other form of non-smtp connectivity that's
broken. ssh to the same host is fine, for example. But smtps on port 465
also seems not to work.
On another provider (fastmail) I was able to workaround the problem as
they run an smtps server you can connect to on port 443, which does seem
to have fixed the problem there.
Joseph