problems retrieving mail again

[tom koehler]

I thought the problem went away - it did, then came back - come and gone in
fact, a couple of times.
imac, running OS 10.6.8 and stock mail program, no adjustments or fiddling on
my part. I just came from my webmail, and I know there are two messages
there. Just tried to fetch them with mac mail, and bupkis.

Mail connection doctor info dump follows:


CONNECTED Apr 24 22:07:15.093 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290

READ Apr 24 22:07:15.372 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK POP3 ready


WROTE Apr 24 22:07:15.374 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
CAPA


READ Apr 24 22:07:15.419 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK Capability list follows

EXPIRE 31 USER

TOP

UIDL

USER

XOIP

.


WROTE Apr 24 22:07:15.423 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
USER tvko...@frontiernet.net


READ Apr 24 22:07:15.468 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK


WROTE Apr 24 22:07:15.472 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
PASS *******


READ Apr 24 22:07:15.901 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK maildrop ready, 2 messages (17390 octets) (42741)


WROTE Apr 24 22:07:15.904 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
STAT


READ Apr 24 22:07:16.044 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK 2 17390


WROTE Apr 24 22:07:16.047 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
UIDL


READ Apr 24 22:07:16.185 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK 2 messages (17390 octets)

1 ANtlimIAAAoqUXhdRgAAAAMnBtA

2 AKlYimIAAQ9mUXiVSA0fEnfonTE

.


WROTE Apr 24 22:07:16.190 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
LIST


READ Apr 24 22:07:16.378 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK 2 messages (17390 octets)

1 3839

2 13551

.


WROTE Apr 24 22:07:16.383 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
RETR 1


READ Apr 24 22:07:16.537 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
-ERR [SYS/TEMP] problem retrieving message.


WROTE Apr 24 22:07:16.542 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
TOP 1 0


READ Apr 24 22:07:16.681 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
-ERR [SYS/TEMP] problem retrieving message.


WROTE Apr 24 22:07:16.686 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
RETR 1


READ Apr 24 22:07:16.826 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
-ERR [SYS/TEMP] problem retrieving message.


WROTE Apr 24 22:07:16.832 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
QUIT


READ Apr 24 22:07:17.065 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:pop3.frontiernet.net -- port:995 -- socket:0x11e05d7a0 --
thread:0x1199c2290
+OK server signing off.

##############################

so, as I'm composing this article, mail program goes after the mail again,
with same results, no mail - even though there are two messages there.

I do not know what kinds of questions to ask - is there a problem with the
software, or is there a problem with my ISP? I tend to favor blaming the ISP,
because it is not a particularly good one, but is the only game in town.

tom koehler

--
I will find a way or make one.

[Chris Ridd]

The POP server being run by your ISP is malfunctioning. You can
authenticate to it OK, you can list messages, but trying to retrieve
them gives an "-ERR [SYS/TEMP] problem retrieving message." instead.
That message is coming from the server. You could send them the above
transcript to show them.

I think you need to complain to the ISP. Alternatively, see if your ISP
supports IMAP instead - that might (long shot) be running on a
different and working server.

Or consider using an external mail provider like gmail. There's a way
to use your existing email address if you use gmail.

--
Chris

[tom koehler]

On Thu, 25 Apr 2013 1:05:13 -0500, Chris Ridd wrote
(in message <atrvcn...@mid.individual.net>):

> On 2013-04-25 03:15:11 +0000, tom koehler said:
>
>> I thought the problem went away - it did, then came back - come and gone in
>> fact, a couple of times.
>> imac, running OS 10.6.8 and stock mail program, no adjustments or fiddling
>> on
>> my part. I just came from my webmail, and I know there are two messages
>> there. Just tried to fetch them with mac mail, and bupkis.
>>
>> Mail connection doctor info dump follows:
>>

>

> The POP server being run by your ISP is malfunctioning. You can
> authenticate to it OK, you can list messages, but trying to retrieve
> them gives an "-ERR [SYS/TEMP] problem retrieving message." instead.
> That message is coming from the server. You could send them the above
> transcript to show them.
>
> I think you need to complain to the ISP. Alternatively, see if your ISP
> supports IMAP instead - that might (long shot) be running on a
> different and working server.
>
> Or consider using an external mail provider like gmail. There's a way
> to use your existing email address if you use gmail.
>
>

Thanks so much for this information, Chris! I've got a mad on for this ISP,
but it is the only game in town, until we get fiber. I'm going to contact my
ISP forthwith. I will include a copy of the info dump.

[Jamie Kahn Genet]

I agree with Chris - move to a third party email provider like Google,
Yahoo or Fastmail. Google's Google Apps webmail, IMAP and POP email
service is what I use - free, or very low cost depending on your needs,
and I can use my own domain name too.
--
If you're not part of the solution, you're part of the precipitate.

[tom koehler]

On Thu, 25 Apr 2013 21:28:51 -0500, Jamie Kahn Genet wrote
(in message <1l1xusb.24kckxifpls0N%jam...@wizardling.geek.nz>):

I had a chat with my ISP tech service person and she told me they were aware
of this problem and Yahoo was working on it. Although my service provider is
Frontier, that company has seen fit to have Yahoo do whatever it does to make
mail happen. It was not always this way, but apparently this was a way of
saving a few dollars for Frontier. I do not savvy what happened, but
apparently Yahoo has been providing whatever it does for my e-mail from
Frontier.

E-mail service was fully restored soon after my chat with the tech, and so
order has been restored to the universe again. For the time being.

Frontier *is* The Phone Company here. They own the hardware, the lines and
poles and all else that enables my household to connect to the outer world.
Our community is in the process of building a fiber-to-the-house network for
the whole county, and when it goes live, Frontier is history. Even if I were
to go to another party for e-mail service, I am still tied to the Frontier
infrastructure, which is under-sized, under-powered, and prone to erratic or
indifferent service, for a hundred beans per month.

Once again, I thank all of you here, for your generosity in giving me your
time and your expertise in the solving of my various problems over the years.
I do not doubt that I will be back for more help when the need arises.
tom koehler, on the northern shore of Lake Superior