From: Mark Hobley on
On Mon, 14 Jun 2010 01:02:21 +0100, Theo Markettos wrote:

>
>> I am not sure how to switch to port 587 (in this case my mail client is
>> Debian reportbug, which makes a direct connection via smtp.)
>
> By default it seems to use sendmail or whatever fulfills that function
> on your machine. If you want it to send direct, you need to add:
> --smtphost=HOST[:PORT]
> to the command line. You can also configure this permanently if you
> wish.

I haven't got a working mail transport agent on this machine at this
time. The reportbug tool communicates directly with the external smtp
server hosted by Three Mobile.

--
/local/home/mark/.Signature

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Mark Hobley on
On Mon, 14 Jun 2010 01:17:58 +0100, The Natural Philosopher wrote:

> One thing I did find, is that 3 mobiles DNS servers were not fit for
> purpose. I installed BIND as a local DNS proxy server.

I had the same problem. I am using the DNS servers provided by Google at
the moment, until I can find one in Great Britain.

Mark.

> frankly the whole affair merely proved to me that where I needed mobile
> internet - away from my usual places of work - it didn't actually work.
>
> I returned the loaned dongle to its owner, who wryly observed 'didn't
> work for you, either huh?' :-)

I have a relatively complicated setup here, my network is ethernet, this
goes via a router, which originally went to a cable modem. I have removed
the cable modem, and I now use a broadband router, which has a mobile
dongle plugged into the back. The broadband router makes the connection
to the internet via the Three Mobile dongle.

--
/local/home/mark/.Signature

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Dave U. Random on
"MH" =3D=3D Mark Hobley <markhob...(a)yahoo.donottypethisbit.co>:
MH> Three mobile is a real pain, because outgoing smtp is
MH> blocked to any other provider "for security reasons", so
MH> my only choice is to use their relay.

I can think of at least two options to circumvent your
provider's restrictions:

Get an account whith some email provider that listens for
SMTP connections at some non-standard ports, ie. ports
other than 25 and 465. Use that account for outgoing
mail (ie. mail delivery). You will have to use SMTP
authentication and SSL/TLS encryption. Then instruct
the mail transport agent on your machine to use the SMTP
server(s) of the new provider.

If the above is not an option for some reason and you have
a shell account on some other machine (say, boxA) with internet
access, tell your mail transport agent to use something like
ssh your_account(a)boxA /usr/sbin/sendmail $RECIPIENT...
for mail delivery. It isn't as easy as the first option, ie.
playing with the SMTP server (smarthost) variable in some
configuration file, but it does work.