Hi out there
Thanks to the great help I got a couple of months ago, I can now
happily send emails from alpine wherever it is, on a Mac, a PC or
laptop running Debian, even on my Pinephone running Mobian. All good.
Well, not ALL, exactly, because now I'd like to be able to RECEIVE some
mail too.
I'm getting closer, and this time round have got stuck with a message I
don't understand, nor has a Duck-Duck search helped. Alpine seems to be launching well, asks for the password, seems happy with it, but then I
get:
"Unexpected tagged response"
or more fully:
{mail.tpg.com.au:110/notls/user=address@tpg.com.au}INBOX : unexpected
tagged response
On Fri, 27 Aug 2021, Nikki wrote:
Hi out there
Thanks to the great help I got a couple of months ago, I can now
happily send emails from alpine wherever it is, on a Mac, a PC or
laptop running Debian, even on my Pinephone running Mobian. All good.
Well, not ALL, exactly, because now I'd like to be able to RECEIVE some >>mail too.
I'm getting closer, and this time round have got stuck with a message I >>don't understand, nor has a Duck-Duck search helped. Alpine seems to be >>launching well, asks for the password, seems happy with it, but then I
get:
"Unexpected tagged response"
or more fully:
{mail.tpg.com.au:110/notls/user=address@tpg.com.au}INBOX : unexpected >>tagged response
port 110 is an insecure port for POP. Although Alpine will connect you to >that port, Alpine is not a good pop client. I would recommend that you
change the previous definition from
{mail.tpg.com.au:110/notls/user=address@tpg.com.au}INBOX
to
{mail.tpg.com.au/ssl/user=address@tpg.com.au}INBOX
the definition you have will leak your username and password. I will not
help you fix it so your credentials be stolen. The fix I am giving you
will work better for you.
I hope this helps.
I am in no way disputing your sound advice, that sending credentials in
the clear over an insecure connection is undesireable and that the OP
should instead use a secure connection.
But what does the error message mean? What was tagged unexpectedly?
I will pitch the use of IMAP as a preferred alternative to POP wherever
it's available. pine/alpine implements IMAP perfectly as the two grew up together.
On Fri, 27 Aug 2021, Adam H. Kerman wrote:
I am in no way disputing your sound advice, that sending credentials in
the clear over an insecure connection is undesireable and that the OP >>should instead use a secure connection.
But what does the error message mean? What was tagged unexpectedly?
I will pitch the use of IMAP as a preferred alternative to POP wherever >>it's available. pine/alpine implements IMAP perfectly as the two grew up >>together.
the configuration sent by the OP is for an insecure connection to an IMAP >server, however, the server in port 110 is a pop server. . . .
Thanks Eduardo, for the advice and also the caveats. Rest assured I used
a fresh (and hence empty installation) on a computer I don't generally
use, a nom de plume, and an email address reserved for the learning
process ... so they'll never get my recipe for Crespelle alla Fiorentina
this way!
I'd tried ssl before but TPG refused it; I expect it clashed with the
port number, so I've learned from your advice, headless chicken that I
am -- in this subject area at least. Yes I'll admit I'm unsure whether
I'm IMAP or POP and would have called TPG support, but for the fact they
ring off as soon as you mention the word "Linux".
BTW: I do know something about POP and IMAP and the mails being stored
on either their server, on the my machine. Is that all there is to that distinction?
And I thought to declare my choice by using the port number.
Sorry if I'm wasting your time. I'll go back to basics.
On Fri, 27 Aug 2021, Nikki wrote:
Hi out there
Thanks to the great help I got a couple of months ago, I can now
happily send emails from alpine wherever it is, on a Mac, a PC or
laptop running Debian, even on my Pinephone running Mobian. All good.
Well, not ALL, exactly, because now I'd like to be able to RECEIVE some mail too.
I'm getting closer, and this time round have got stuck with a message I don't understand, nor has a Duck-Duck search helped. Alpine seems to be launching well, asks for the password, seems happy with it, but then I
get:
"Unexpected tagged response"
or more fully:
{mail.tpg.com.au:110/notls/user=address@tpg.com.au}INBOX : unexpected tagged response
port 110 is an insecure port for POP. Although Alpine will connect you to that port, Alpine is not a good pop client. I would recommend that you
change the previous definition from
{mail.tpg.com.au:110/notls/user=address@tpg.com.au}INBOX
to
{mail.tpg.com.au/ssl/user=address@tpg.com.au}INBOX
the definition you have will leak your username and password. I will not
help you fix it so your credentials be stolen. The fix I am giving you
will work better for you.
I hope this helps.
I'd tried ssl before but TPG refused it; I expect it clashed with the[SNIP]
On Sun, 29 Aug 2021, Nikki wrote:
Thanks Eduardo, for the advice and also the caveats. Rest assured I used
a fresh (and hence empty installation) on a computer I don't generally
use, a nom de plume, and an email address reserved for the learning
process ... so they'll never get my recipe for Crespelle alla Fiorentina this way!
Getting email passwords insecurely also has to do hacking into services.
Your provider could be hacked, and someone on your behalf could break
havoc. In some other providers it could also give access to the hacker to other resources of yours, like files you store in the service, and much
more.
I'd tried ssl before but TPG refused it; I expect it clashed with the
port number, so I've learned from your advice, headless chicken that I
am -- in this subject area at least. Yes I'll admit I'm unsure whether
I'm IMAP or POP and would have called TPG support, but for the fact they ring off as soon as you mention the word "Linux".
I can connect to ssl securely, but I do not have a username and password
to use. If you call your provider, ask them what is the username you
should use to login in IMAP using, say, Thunderbird. Let's say that they
say "foo", then you should set Alpine to use the definition
{mail.tpg.com.au/ssl/user=foo}INBOX
and then enter your password (my hunch is that foo is the local part of
you email address foo@tpg.com.au)
On the other hand, when I go to
https://www.tpg.com.au/support/email_settings.html
I read that you only have insecure connections available (shiver!) In that case get ready to lose your secret recipe for Crespelle alla Fiorentina.
If that is the case, then your configuration for your inbox should
be
{mail.tpg.com.au/user=foo}INBOX
BTW: I do know something about POP and IMAP and the mails being stored
on either their server, on the my machine. Is that all there is to that distinction?
No, there is more to the distinction, and Alpine does not store your
emails in your local machine at any time. Alpine always accesses your
email remotely.
And I thought to declare my choice by using the port number.
You must tell alpine the protocol and port to connect, since you only told alpine the port and not the protocol, Alpine used imap, because that is
what it does when you do not specify the protocol.
Sorry if I'm wasting your time. I'll go back to basics.
This should be easy to configure, but I do not have the information I
need.
On 29/08/2021 01:21, Nikki wrote:
[SNIP]
I'd tried ssl before but TPG refused it; I expect it clashed with the[SNIP]
Late noticing this, but:
Is TPG your RSP or MSP??
If they are your RSP you do *not* have IMAP access to your mailbox, it
is simple POP3 and can only be accessed directly from within the TPG
network. (I use getmail to pull stuff out of my TPG mailbox, I just use
the SimplePOP3Receiver, I've never worried about securing it.)
A bit of checking reminds me that it supports SSL connections but not
with an encrypted password.
If they are your MSP - i.e. you have purchased this: <https://www.tpg.com.au/products_services/imap.php> for forty quid a
year - then you have IMAP access.
Cheers,
Gary B-)
In article <8kdrvh-9s7.ln1@paranoia.mcleod-schmidt.id.au>, Gary R.
Schmidt <grschmidt@acm.org> wrote:
On 29/08/2021 01:21, Nikki wrote:
[SNIP]
Late noticing this, but:
I'd tried ssl before but TPG refused it; I expect it clashed with the[SNIP] >>
Is TPG your RSP or MSP??
If they are your RSP you do *not* have IMAP access to your mailbox, it
is simple POP3 and can only be accessed directly from within the TPG
network. (I use getmail to pull stuff out of my TPG mailbox, I just use
the SimplePOP3Receiver, I've never worried about securing it.)
A bit of checking reminds me that it supports SSL connections but not
with an encrypted password.
If they are your MSP - i.e. you have purchased this:
<https://www.tpg.com.au/products_services/imap.php> for forty quid a
year - then you have IMAP access.
Cheers,
Gary B-)
Hi Gary, and thanks for your comments. I'm with TPG as an NBN bundle,
and frankly I can't answer your question, or even say what the acronyms
stand for. RSP I assume (after a spot of DuckDucking) is "remote
service platform". MSP?
The fact is I've not really had to understand much about email before.
I moved to TPG (from Internode) as an aspect of moving to NBN, and
looked on it as a package deal, no MSP ingredient that I'm aware of. No
extra $40.
Maybe I should have my email accounts at Protonmail. Any thoughts on
them?
I'd hoped 'alpine' would be an all-in-one affair I could use in a CLI environment, and as far as using 'getmail' or any of those utilities to
deal with mail, I clearly have a heap of learning to do. BTW: advice
about where to do that would be appreciated.
For context: I'm a long term MacOS user, and having toyed with Linux
for some time, am looking to take it seriously and abandon the Apple
Universe if-and-wherever possible.
I don't think you are an Alpine user.
I use Thunderbird on Solaris, Linux, and Windows, it just works, and I don't have to think too hard about what I am doing. (I use LookOut! in my day job, that's the problem with having to earn a living!!)
Hi out there
Thanks to the great help I got a couple of months ago, I can now
happily send emails from alpine wherever it is, on a Mac, a PC or
laptop running Debian, even on my Pinephone running Mobian. All good.
Well, not ALL, exactly, because now I'd like to be able to RECEIVE some
mail too.
I'm getting closer, and this time round have got stuck with a message I
don't understand, nor has a Duck-Duck search helped. Alpine seems to be launching well, asks for the password, seems happy with it, but then I
get:
"Unexpected tagged response"
or more fully:
{mail.tpg.com.au:110/notls/user=address@tpg.com.au}INBOX: unexpected
tagged response
Dear Nikki,
based on the input you and others have given, I suggest that you change
your configuration of your inbox-path to
{mail.tpg.com.au/pop3/user=address@tpg.com.au}INBOX
I hope this works.
. . .
Some history: Pine was/is an email client (Mail User Agent, MUA)
developed back in the days (1992) when email systems were all internal
and when something went wrong you wandered down/up stairs to where the
people managing your servers sat and asked what was going on.
Alpine is a continuation of Pine, it was supposed to be easier to use
than Pine,
but, IMNSHO it's just as opaque.
(Note: I fiddle with alpine
from time to time, but there are problems getting it to play nicely with
my Panda-IMAP changes - see, that's the sort of stuff that happens when
you get into weird bollocks like alpine - so I don't use it in anger.)
Things like Alpine work best in a fully controlled environment, where
you run your own mail-server and know just what every little bit and
byte is doing, if you *know* how email works, it'd be fine.
If you have some overwhelming need to run a CLI environment - such as
being on the end of a noisy telephone line - then it might even be
necessary, but it certainly can be a rod for your back.
. . .
Alpine is a continuation of Pine, it was supposed to be easier to use
than Pine, but, IMNSHO it's just as opaque. (Note: I fiddle with alpine
from time to time, but there are problems getting it to play nicely with
my Panda-IMAP changes - see, that's the sort of stuff that happens when
you get into weird bollocks like alpine - so I don't use it in anger.)
On Sun, 29 Aug 2021, Eduardo Chappa wrote:
Dear Nikki,
based on the input you and others have given, I suggest that you change your configuration of your inbox-path to
{mail.tpg.com.au/pop3/user=address@tpg.com.au}INBOX
I hope this works.
And if that does not work try
{mail.tpg.com.au/pop3/user=address}INBOX
instead (here "address" is the local part of "address@tpg.com.au".
I don't think you are an Alpine user.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 53:50:36 |
Calls: | 6,712 |
Files: | 12,243 |
Messages: | 5,355,274 |