I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs in command-line mode. When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs
ater I have re-started the router. I am due to move to a new ISP in a
couple of weeks, so do not want to start any correspondence with my
current ISP.
Liz Tuddenham wrote:
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs in command-line mode. When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs ater I have re-started the router. I am due to move to a new ISP in a couple of weeks, so do not want to start any correspondence with my
current ISP.
Is the ubunto install on DHCP, or manual IP configuration?
if the former, it should get DNS setting from your router, if the latter
have you configured DNS server IPs for it?
if you haven't got a GUI installed, you'll probably need to edit /etc/resolv.conf
by hand
or possibly
/etc/netplan/somethingorother.yaml
I am just coming to> terms with the command line interface (the lasttime I used one it was
on a Teletype).OK, welcome to a vertical learning curve.
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs
in command-line mode. When I try to download any further files
(including a GUI) I get a lot of "Temporary failure resolving ...."
errors.
This happens with a wireless or an Ethernet connection and still
occurs ater I have re-started the router. I am due to move to a new
ISP in a couple of weeks, so do not want to start any correspondence
with my
current ISP.
Liz Tuddenham wrote:
I am just coming to> terms with the command line interface (the lasttime I used one it was
on a Teletype).OK, welcome to a vertical learning curve.
Are you logged in as root?
What do you see if you type
cat /etc/resolv.conf
and hit return
Do you know what editor(s) you've got installed? vi? nano?
Andy Burns <usenet@andyburns.uk> wrote:try
Do you know what editor(s) you've got installed? vi? nano?
How do I find that?
18 lines of text which I cannot expoer in any way, so I would have to
type them all out by hand. The main bits appear to be:
nameserver 127.0.0.53
Small point make very sure you are installing the correct version of Ubuntu for you hardware and processor, e.g., ARM or AMD, Intel etc.
This, is the most important requirement !
Liz Tuddenham wrote:
Andy Burns <usenet@andyburns.uk> wrote:
Do you know what editor(s) you've got installed? vi? nano?
How do I find that?try
nano testfile
first
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
OK, so you have both nano and vi. I like vi, but if you didn't startnano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of the
screen.
Liz Tuddenham wrote:
nano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of theOK, so you have both nano and vi. I like vi, but if you didn't start
screen.
using it several decades ago, you'll probably hate it, so I'd say stick
to using nano for now :-)
first off take a backup copy of your resolver config file
cp /etc/resolv.conf /etc/resolv.bak
Andy Burns wrote:You're not logged in as root then, you need to be ...
cp /etc/resolv.conf /etc/resolv.bak
Fell at the first hurdle:
cp: cannot create regular file 'etc/resolve.bak' : permission denied
You're not logged in as root then, you need to be ...
Andy Burns wrote:
You're not logged in as root then, you need to be ...
Or maybe ubuntu prefers sudo, try
sudo cp /etc/resolv.conf /etc/resolv.bak
then if that works
sudo nano /etc/resolv.conf
edit, save and exit as discussed before ...
Liz Tuddenham wrote:
nano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of theOK, so you have both nano and vi. I like vi, but if you didn't start
screen.
using it several decades ago, you'll probably hate it, so I'd say stick
to using nano for now :-)
first off take a backup copy of your resolver config file
cp /etc/resolv.conf /etc/resolv.bak
then edit the original
nano /etc/resolv.conf
it should be a fairly simple job to edit the line that says
nameserver 127.0.0.53
and make it say
nameserver 8.8.8.8
then save changes (ctrl-O)
and exit (ctrl-X)
when back at a prompt, see if you can e.g.
ping www.bbc.co.uk
if so your downloads stand half a chance ...
Andy Burns <usenet@andyburns.uk> wrote:
Liz Tuddenham wrote:
nano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of theOK, so you have both nano and vi. I like vi, but if you didn't start
screen.
using it several decades ago, you'll probably hate it, so I'd say stick
to using nano for now :-)
first off take a backup copy of your resolver config file
cp /etc/resolv.conf /etc/resolv.bak
then edit the original
nano /etc/resolv.conf
it should be a fairly simple job to edit the line that says
nameserver 127.0.0.53
and make it say
nameserver 8.8.8.8
then save changes (ctrl-O)
and exit (ctrl-X)
when back at a prompt, see if you can e.g.
ping www.bbc.co.uk
if so your downloads stand half a chance ...
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:
ping: www.bbc.co.uk: Temporary failure in name resolution
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini.
It runs in
command-line mode.
When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs
ater I have re-started the router. I am due to move to a new ISP in a
couple of weeks, so do not want to start any correspondence with my
current ISP.
On 2026-10-19 11:59, Liz Tuddenham wrote:
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini.
What version Ubuntu Server?
It runs in
command-line mode.
If that is a problem to you, I would advise simply starting again with
Ubuntu Desktop.
When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs ater I have re-started the router. I am due to move to a new ISP in a couple of weeks, so do not want to start any correspondence with my
current ISP.
Yes, I'm afraid this seems to be a common problem with IP4 on various versions of Ubuntu, I think IP6 may actually work, but, because here in Scotland, I use a mobile broadband connection which doesn't support IP6,
I can't actually tell.
As far as IP4 is concerned, almost certainly the fix will vary with what version you have installed. I have fixes for versions 16 and 18 which I
give below, but you've probably installed a later version, and it's
possible that neither will work.
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs in command-line mode. When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
Have done this with "sudo" prefix as suggested.I agree, to save your own time, nuke it and start again with a GUI
It seemed to go as described but the result was:
ping:www.bbc.co.uk: Temporary failure in name resolution
Liz Tuddenham wrote:
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:I agree, to save your own time, nuke it and start again with a GUI
ping:www.bbc.co.uk: Temporary failure in name resolution
Liz Tuddenham wrote:
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:I agree, to save your own time, nuke it and start again with a GUI
ping:www.bbc.co.uk: Temporary failure in name resolution
Liz Tuddenham wrote:
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:I agree, to save your own time, nuke it and start again with a GUI
ping:www.bbc.co.uk: Temporary failure in name resolution
Andy Burns wrote:Glad it's working, although I've run my own email servers at home and in data-centres, I no longer do that for myself, or for customers, there's
to save your own time, nuke it and start again with a GUI
I'm pleased to follow this up with some good news: I downloaded a GUI
and gave a knowledgeable friend remote access to the machine. He set it
up as an e-mail server and it now appears to be working well.
6IFR1ZGRlbmhhbSB3cm90ZToNCg0KPiBBbmR5IEJ1cm5zIHdyb3RlOg0KPiANCj4+IHRv IHNhdmUgeW91ciBvd24gdGltZSwgbnVrZSBpdCBhbmQgc3RhcnQgYWdhaW4gd2l0aCBhIEdV SQ0KPiANCj4gSSdtIHBsZWFzZWQgdG8gZm9sbG93IHRoaXMgdXAgd2l0aCBzb21lIGdvb2Qg bmV3czogIEkgZG93bmxvYWRlZCBhIEdVSQ0KPiBhbmQgZ2F2ZSBhIGtub3dsZWRnZWFibGUg ZnJpZW5kIHJlbW90ZSBhY2Nlc3MgdG8gdGhlIG1hY2hpbmUuICBIZSBzZXQgaXQNCj4gdXAg YXMgYW4gZS1tYWlsIHNlcnZlciBhbmQgaXQgbm93IGFwcGVhcnMgdG8gYmUgd29ya2luZyB3 ZWxsLg0KR2xhZCBpdCdzIHdvcmtpbmcsIGFsdGhvdWdoIEkndmUgcnVuIG15IG93biBlbWFp bCBzZXJ2ZXJzIGF0IGhvbWUgYW5kIGluIA0KZGF0YS1jZW50cmVzLCBJIG5vIGxvbmdlciBk byB0aGF0IGZvciBteXNlbGYsIG9yIGZvciBjdXN0b21lcnMsIHRoZXJlJ3MgDQphIGxvdCB0 byBjb25zaWRlciBhbmQgYSByaXNrIG9mIGl0IGVhdGluZyB0aW1lIHdoZW4gSSBkb24ndCBo YXZlIGFueSBzcGFyZS4NCg0KU28gSSBub3cgdXNlIChhbmQgcmVjb21tZW5kKSB2YXJpb3Vz IGNvbWJpbmF0aW9ucyBvZiBteXRoaWMgYmVhc3RzIGFuZCANCm1pY3Jvc29mdDM2NSBhcyBl eHRlcm5hbCBwcm92aWRlcnMuICBEb24ndCBwdXQgdG9vIG11Y2ggYnVyZGVuIG9uIHlvdXIg DQpmcmllbmQgZm9yIHRoZSBzYWtlIG9mIMKjMjAveWVhciAuLi4gZmFzdGhvc3RzIGRvIHNp bWlsYXIgdGhpbmdzIGF0IA0Kc2ltaWxhciBwcmljZXMuDQo
Andy Burns wrote:Sorry, thunderbird occasionally does that, usually because it's seen a non-ASCII character it doesn't like, though I can't actually see what triggered it in your message that I was replying to, reposted below ...
[base64 encoded message]
Couldn't read your reply.
I'm pleased to follow this up with some good news: I downloaded a GUI
and gave a knowledgeable friend remote access to the machine. He set it
up as an e-mail server and it now appears to be working well.
Couldn't read your reply.Sorry thunderbird found something it can't cope with - twice.
Couldn't read your reply.Sorry, thunderbird occasionally does that, usually because it's seen a non-ASCII character it doesn't like, though I can't actually see what triggered it in your message that I was replying to ...
Andy Burns wrote:
thunderbird occasionally does that, usually because it's seen anon-ASCII character it doesn't like, though I can't actually see what
triggered it in your message that I was replying to ...
I'm guessing it's the pound sign.
It's not so much a non-ASCII character that Thunderbird doesn't like, as
a non-ASCII character that Thunderbird thinks someone else won't like.
It handles it correctly, and most other news clients can cope with the result.
In an ideal world all EMail transport would use UTF-8 and we wouldn't
have to worry about Content-Transfer-Encoding headers ... but there's probably STILL a mail server somewhere that can only cope with 7 bits ...
Liz Tuddenham wrote:
Andy Burns wrote:Glad it's working, although I've run my own email servers at home and
to save your own time, nuke it and start again with a GUII'm pleased to follow this up with some good news: I downloaded a
GUI
and gave a knowledgeable friend remote access to the machine. He set it
up as an e-mail server and it now appears to be working well.
in data-centres, I no longer do that for myself, or for customers,
there's a lot to consider and a risk of it eating time when I don't
have any spare.
So I now use (and recommend) various combinations of mythic beasts and microsoft365 as external providers. Don't put too much burden on your
friend for the sake of -u20/year ... fasthosts do similar things at
similar prices.
On 01/11/2026 09:31, Andy Burns wrote:
Couldn't read your reply.Sorry, thunderbird occasionally does that, usually because it's seen a non-ASCII character it doesn't like, though I can't actually see what triggered it in your message that I was replying to ...
I'm guessing it's the pound sign.
It's not so much a non-ASCII character that Thunderbird doesn't like, as
a non-ASCII character that Thunderbird thinks someone else won't like.
It handles it correctly, and most other news clients can cope with the result.
In an ideal world all EMail transport would use UTF-8 and we wouldn't
have to worry about Content-Transfer-Encoding headers ... but there's probably STILL a mail server somewhere that can only cope with 7 bits ...
On 01/11/2026 09:31, Andy Burns wrote:
Couldn't read your reply.Sorry, thunderbird occasionally does that, usually because it's seen
a non-ASCII character it doesn't like, though I can't actually see
what triggered it in your message that I was replying to ...
I'm guessing it's the pound sign.
It's not so much a non-ASCII character that Thunderbird doesn't like,
as a non-ASCII character that Thunderbird thinks someone else won't
like. It handles it correctly, and most other news clients can cope
with the result.
In an ideal world all EMail transport would use UTF-8 and we wouldn't
have to worry about Content-Transfer-Encoding headers ... but there's probably STILL a mail server somewhere that can only cope with 7 bits
...
Daniel James <daniel@me.invalid> wrote:
On 01/11/2026 09:31, Andy Burns wrote:
Couldn't read your reply.Sorry, thunderbird occasionally does that, usually because it's seen a
non-ASCII character it doesn't like, though I can't actually see what
triggered it in your message that I was replying to ...
I'm guessing it's the pound sign.
It's not so much a non-ASCII character that Thunderbird doesn't like, as
a non-ASCII character that Thunderbird thinks someone else won't like.
It handles it correctly, and most other news clients can cope with the
result.
In an ideal world all EMail transport would use UTF-8 and we wouldn't
have to worry about Content-Transfer-Encoding headers ... but there's
probably STILL a mail server somewhere that can only cope with 7 bits ...
I'm using MacSOUP 2.4.6 on OS 8.6 and the Usenet standard hasn't changed since I installed it.
I'm using MacSOUP 2.4.6 on OS 8.6 and the Usenet standard hasn't changed since I installed it.RFC 5536 refers to RFC 2045
NNTP is 8-bit clean; encoding isnrCOt needed for news articles (even if it might be for email). If it is used then quoted-printable is much more sensible than base64. IMO Thunderbird using base64 in news is a bug.But unlikely to get fixed in a hurry ...
Richard Kettlewell wrote:
NNTP is 8-bit clean; encoding isnrCOt needed for news articles (even if it >> might be for email). If it is used then quoted-printable is much more
sensible than base64. IMO Thunderbird using base64 in news is a bug.
But unlikely to get fixed in a hurry ...
Andy Burns <usenet@andyburns.uk> writes:
Richard Kettlewell wrote:
NNTP is 8-bit clean; encoding isnrCOt needed for news articles (even if it >>> might be for email). If it is used then quoted-printable is much more
sensible than base64. IMO Thunderbird using base64 in news is a bug.
But unlikely to get fixed in a hurry ...
It is not a bug, the base 64 was in a mime part which is in the
standard.
Richmond <dnomhcir@gmx.com> writes:
Andy Burns <usenet@andyburns.uk> writes:
Richard Kettlewell wrote:
NNTP is 8-bit clean; encoding isnrCOt needed for news articles (even if it >>>> might be for email). If it is used then quoted-printable is much more
sensible than base64. IMO Thunderbird using base64 in news is a bug.
But unlikely to get fixed in a hurry ...
It is not a bug, the base 64 was in a mime part which is in the
standard.
Not every bug is a standards violation.
Richard Kettlewell <invalid@invalid.invalid> writes:
Richmond <dnomhcir@gmx.com> writes:
Andy Burns <usenet@andyburns.uk> writes:
Richard Kettlewell wrote:
NNTP is 8-bit clean; encoding isnrCOt needed for news articles (even if it
might be for email). If it is used then quoted-printable is much more >>>>> sensible than base64. IMO Thunderbird using base64 in news is a bug.
But unlikely to get fixed in a hurry ...
It is not a bug, the base 64 was in a mime part which is in the
standard.
Not every bug is a standards violation.
No, and using Base 64 is not a bug.
Richard Kettlewell <invalid@invalid.invalid> writes:
Richmond <dnomhcir@gmx.com> writes:No, and using Base 64 is not a bug.
Andy Burns <usenet@andyburns.uk> writes:
Richard Kettlewell wrote:
NNTP is 8-bit clean; encoding isnrCOt needed for news articles (even if itBut unlikely to get fixed in a hurry ...
might be for email). If it is used then quoted-printable is much more >>>>>> sensible than base64. IMO Thunderbird using base64 in news is a bug. >>>>
It is not a bug, the base 64 was in a mime part which is in the
standard.
Not every bug is a standards violation.
[Too much quoting, just to keep the context]
I think it depends very much on what you consider constitutes a bug.
Given that NNTP is 8-bit tolerant there is no need for ANY transport
encoding (for any content that can be considered to be text, anyway)
-- everything can just be sent as UTF-8.
Base64 encoding is permitted, certainly, but it is unnecessary, and
may cause a message to be inaccessible to the recipient (as is
apparently the case here) and so it is undesirable.
QP encoding is also unnecessary, but it would (at least in this case)
leave most of the message legible even without decoding, so it is
preferable to Base64 encoding, but still undesirable.
I suspect the code in Thunderbird treats EMail and news messages as essentially the same -- in many respects they are the same -- and
because SMTP still should be assumed to be 100% 8-bit clean it sends
all non-ASCII messages with transport encoding regardless of whether
they are mail or news. This is arguably a bug, as the encoding is only
needed for EMail.
NNTP is pretty-much a minority concern, these days, so I don't see
anyone changing that behaviour.
I think it depends very much on what you consider constitutes a bug.
Given that NNTP is 8-bit tolerant there is no need for ANY transport
encoding (for any content that can be considered to be text, anyway)
-- everything can just be sent as UTF-8.
Base64 encoding is permitted, certainly, but it is unnecessary, and
may cause a message to be inaccessible to the recipient (as is
apparently the case here) and so it is undesirable.
The point of AndyrCOs post was to communicate something (to
Liz specifically as well as publicly), and Liz canrCOt read it because Thunderbird has, completely unnecessarily, used an encoding that LizrCOs newsreader doesnrCOt understand. Thunderbird is plainly not meeting its usersrCO needs on this particular point, in a way that is immediately foreseeable to anyone even slightly familiar with the problem domain.
Incidentally the MIME specification does recognize this, at least
informally preferring quoted-printable for predominantly ASCII data, as
in AndyrCOs post, precisely because it degrades gracefully when read by a pre-MIME client (which are rather common in Usenet).
https://www.rfc-editor.org/info/rfc2045/#section-6.7
The Quoted-Printable encoding is intended to represent data that
largely consists of octets that correspond to printable characters in
the US-ASCII character set. It encodes the data in such a way that
the resulting octets are unlikely to be modified by mail transport.
If the data being encoded are mostly US-ASCII text, the encoded form
of the data remains largely recognizable by humans.
if only Macs had software that coped with RFC changes from over 33 years ago!
Daniel James <daniel@me.invalid> writes:
I think it depends very much on what you consider constitutes a bug.
Given that NNTP is 8-bit tolerant there is no need for ANY transport
encoding (for any content that can be considered to be text, anyway)
-- everything can just be sent as UTF-8.
Base64 encoding is permitted, certainly, but it is unnecessary, and
may cause a message to be inaccessible to the recipient (as is
apparently the case here) and so it is undesirable.
Right, the starting point of this subthread is exactly the reason I view
it was a bug. The point of AndyrCOs post was to communicate something (to
Liz specifically as well as publicly), and Liz canrCOt read it because >Thunderbird has, completely unnecessarily, used an encoding that LizrCOs >newsreader doesnrCOt understand. Thunderbird is plainly not meeting its >usersrCO needs on this particular point, in a way that is immediately >foreseeable to anyone even slightly familiar with the problem domain.
Incidentally the MIME specification does recognize this, at least
informally preferring quoted-printable for predominantly ASCII data, as
in AndyrCOs post, precisely because it degrades gracefully when read by a >pre-MIME client (which are rather common in Usenet).
https://www.rfc-editor.org/info/rfc2045/#section-6.7
The Quoted-Printable encoding is intended to represent data that
largely consists of octets that correspond to printable characters in
the US-ASCII character set. It encodes the data in such a way that
the resulting octets are unlikely to be modified by mail transport.
If the data being encoded are mostly US-ASCII text, the encoded form
of the data remains largely recognizable by humans.
it was a bug. The point of Andy|ore4raos post was to communicate something (to
Liz specifically as well as publicly), and Liz can|ore4raot read it because >>Thunderbird has, completely unnecessarily, used an encoding that Liz|ore4raos >>newsreader doesn|ore4raot understand. Thunderbird is plainly not meeting its
I use (and choose to use) and old Free Agent. I also only subscribe
to text only groups so E-S suits me fine.
I'm subscribe to quite a lot of groups and the only poster that I
usually cannot read is Andy Burns. I've discussed this before and
elsewhere so what I get is:
the only poster that I usually cannot read is Andy Burns. I've
discussed this before
As he uses User-Agent: Mozilla Thunderbird
then presumably he could readily change it's behaviour but that mayI don't go out of my way to be unreadable, it's not me telling
impact other stuff even though I do not see the need for base64 in a
text only news server.
Trying to change the "mail.strictly_mime" setting, as I can't remember
which way I normally have it set.
an including a pound sign -u as a trigger ...
AnthonyL writes:and 8-bit headers) instead of a normal apostrophe, so far so good.
Richard kettlewell wrote
Andy|ore4raos post
Interestingly (possibly only to me) is the text you quoted above has
garbled up characters. Richard's post included a fancy apostrophe U+2019 (with correct utf-8
According to Google's AI:
-a-a Yes, MacSOUP can handle Content-Transfer-Encoding: base64.
Richmond wrote:
AnthonyL writes:and 8-bit headers) instead of a normal apostrophe, so far so good.
Richard kettlewell wrote
Andy|ore4raos post
Interestingly (possibly only to me) is the text you quoted above has
garbled up characters. Richard's post included a fancy apostrophe U+2019 (with correct utf-8
When AnthonyL quoted Richard, FreeAgent left the the 8-bit characters in
the message, but removed the headers saying that they were there :-(
AnthonyL wrote:
the only poster that I usually cannot read is Andy Burns. I've
discussed this before
Indeed we have
As he uses User-Agent: Mozilla Thunderbird
Doesn't half of usenet?
then presumably he could readily change it's behaviour but that mayI don't go out of my way to be unreadable, it's not me telling
impact other stuff even though I do not see the need for base64 in a
text only news server.
Thunderbird to use base64, it decides for itself based on either
non-ASCII characters I type, or in messages I'm replying to.
Trying to change the "mail.strictly_mime" setting, as I can't remember
which way I normally have it set.
an including a pound sign -u as a trigger ...
David Wade wrote:You're talking about "Google Voice" I presume?
In the US google has a similar feature in its
services, but these are only for US calls ...
I take it you mean for VoIP; from what I remember, the normal Zoom
function was free, though a bit fiddly to set up (I usually let the
other party do that, then invite me).
You've posted in another group, copy/pasted below with headers and I
read those posts fine.
Path: eternal-september.org!nntp.eternal-september.org!feeder.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Andy Burns<usenet@andyburns.uk>
Newsgroups: uk.telecom.broadband,uk.telecom.voip,uk.telecom.broadband Subject: Re: Stupid question are BT still going toi be charginh line
rentalm
after Jan 31st ?
Date: Mon, 2 Nov 2026 15:21:15 +0000
Lines: 14
Message-ID:<nkro3bFhr8U1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
J. P. Gilliver wrote:
David Wade wrote:You're talking about "Google Voice" I presume?
In the US google has a similar feature in itsI take it you mean for VoIP; from what I remember, the normal Zoom
services, but these are only for US calls ...
function was free, though a bit fiddly to set up (I usually let the
other party do that, then invite me).
I don't think it's ever been available in the UK ...
I'm pleased to follow this up with some good news: I downloaded a GUI[re-sending my original reply, with one tweaked thunderbird setting, you
and gave a knowledgeable friend remote access to the machine. He set it
up as an e-mail server and it now appears to be working well.
Liz Tuddenham wrote:
I'm pleased to follow this up with some good news: I downloaded a GUI[re-sending my original reply, with one tweaked thunderbird setting, you might not get a proper pound sign? Nothing I can do about that case,
and gave a knowledgeable friend remote access to the machine. He set it
up as an e-mail server and it now appears to be working well.
but the message as a whole should be more or less readable?]
Glad it's working, although I've run my own email servers at home and in data-centres, I no longer do that for myself, or for customers, there's
a lot to consider and a risk of it eating time when I don't have any spare.
So I now use (and recommend) various combinations of mythic beasts and microsoft365 as external providers. Don't put too much burden on your
friend for the sake of -u20/year ... fasthosts do similar things at
similar prices.
Andy Burns <usenet@andyburns.uk> wrote:
Liz Tuddenham wrote:
I'm pleased to follow this up with some good news: I downloaded a GUI and gave a knowledgeable friend remote access to the machine. He set it up as an e-mail server and it now appears to be working well.[re-sending my original reply, with one tweaked thunderbird setting, you might not get a proper pound sign? Nothing I can do about that case,
but the message as a whole should be more or less readable?]
Glad it's working, although I've run my own email servers at home and in data-centres, I no longer do that for myself, or for customers, there's
a lot to consider and a risk of it eating time when I don't have any spare.
So I now use (and recommend) various combinations of mythic beasts and microsoft365 as external providers. Don't put too much burden on your friend for the sake of |e-u20/year ... fasthosts do similar things at similar prices.
That was perfectly readab, thanks.
The problem is interfacing with Claris Emailer, most hosts refuse to
allow it any more so I am forced to use my own server to relay e-mails
from CEmailer to the outside World.
Liz Tuddenham wrote:
I'm pleased to follow this up with some good news: I downloaded a GUI[re-sending my original reply, with one tweaked thunderbird setting, you >might not get a proper pound sign? Nothing I can do about that case,
and gave a knowledgeable friend remote access to the machine. He set it
up as an e-mail server and it now appears to be working well.
but the message as a whole should be more or less readable?]
Glad it's working, although I've run my own email servers at home and in >data-centres, I no longer do that for myself, or for customers, there's
a lot to consider and a risk of it eating time when I don't have any spare.
So I now use (and recommend) various combinations of mythic beasts and >microsoft365 as external providers. Don't put too much burden on your >friend for the sake of -u20/year ... fasthosts do similar things at
similar prices.
for the sake of -u20/year
Great, I can cope with the pound sign. Hope it doesn't mess other
things up elsewhere (thumbs up, cross fingers)
AnthonyL wrote:
for the sake of -u20/year
Great, I can cope with the pound sign. Hope it doesn't mess other
things up elsewhere (thumbs up, cross fingers)
In your reply the pound sign was left intact, in Liz's reply it got a
bit mangled, but could still be understood.
friend for the sake of |e-u20/year ... fasthosts do similar things at >>similar prices.
Great, I can cope with the pound sign. Hope it doesn't mess other
things up elsewhere (thumbs up, cross fingers)
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:18:28 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |