public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to set up claws mail
Date: Mon, 23 Oct 2017 10:36:34 +0100	[thread overview]
Message-ID: <1876719.iouDLr9l2u@dell_xps> (raw)
In-Reply-To: <20171023094637.4ca690f8@peak.prhnet>

[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]

On Monday, 23 October 2017 09:46:37 BST Peter Humphrey wrote:
> I still don't have it right. On fetching mail this morning I received just
> one message, but webmail showed more than a dozen. A second attempt at
> fetching them left this log entry:
> 
> * Account 'Zen': Connecting to POP3 server: mailhost.zen.co.uk:995...
> [09:35:05] POP3< +OK smarthost03b, Zen Internet POP3 Server Ready
> [09:35:05] POP3> USER peter@prh.myzen.co.uk
> [09:35:05] POP3< +OK Please enter your pass, with the PASS command.
> [09:35:05] POP3> PASS ********
> [09:35:05] POP3< +OK Logged in.
> [09:35:05] POP3> STAT
> [09:35:06] POP3< +OK 13 198521

This shows you have 13 messages totaling 198,521 Bytes

> [09:35:06] POP3> UIDL
> [09:35:06] POP3< +OK UIDL List
> [09:35:06] POP3> LIST
> [09:35:06] POP3< +OK 13 messages (198521 octets)

This doesn't look correct to me.  I would expect to see a list containing each 
message followed by its unique ID, e.g.:

1 00WBw418fblah
2 foo:hdPYR
...
13 whateverswO
.

as per RFC1939 at least.

Also missing is the RETR command, which will retrieve a numbered message and 
the DELE command which will mark the message(s) to be deleted when the client 
quits the session.


> [09:35:06] POP3> QUIT
> [09:35:06] POP3< +OK Goodbye. See you again sometime :)
> 
> Why is claws not fetching those 13 messages?

I can't answer this, other than by saying the above log entries do not display 
a complete transaction sequence I would expect to see between a client and a 
POP3 server.  In the first instance I suggest you use openssl s_client to 
login on a terminal and fire the various commands at the server to see its 
responses.  As long as the server does not error out, run RSET to unmark any 
messages so they are not deleted and QUIT.

Then try again with Claws, increasing the log verbosity to see what you get.  
It may be the POP3 server implementation is incompatible with the Claws 
client, although in 2017 when POP3 would be deemed mature at best, if not 
technologically obsolete, this seems unlikely.


Disclaimer 1:  I have not used Claws for years now.
Disclaimer 2:  I've stopped using telnet to troubleshoot POP3 servers or read 
my emails for even more years than that.  :-)

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-10-23  9:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  9:29 [gentoo-user] How to set up claws mail Peter Humphrey
2017-10-19  9:42 ` Branko Grubic
2017-10-19  9:56   ` Peter Humphrey
2017-10-19 17:27     ` Neil Bothwick
2017-10-19 18:15       ` Mick
2017-10-20  9:15         ` Peter Humphrey
2017-10-20 14:29           ` [gentoo-user] " Grant Edwards
2017-10-20 14:50             ` Peter Humphrey
2017-10-20 15:14               ` Grant Edwards
2017-10-20 15:44               ` Ian Zimmerman
2017-10-21  9:15                 ` Peter Humphrey
2017-10-21  8:43             ` Peter Humphrey
2017-10-20  9:12       ` [gentoo-user] " Peter Humphrey
2017-10-22 12:48         ` Neil Bothwick
2017-10-22 13:59           ` Peter Humphrey
2017-10-22 20:27             ` Neil Bothwick
2017-10-23  8:46               ` Peter Humphrey
2017-10-23  9:22                 ` Neil Bothwick
2017-10-23 12:27                   ` Peter Humphrey
2017-10-23 13:51                     ` Neil Bothwick
2017-10-23 14:39                       ` Peter Humphrey
2017-10-24  0:21                         ` Neil Bothwick
2017-10-24  9:11                           ` Peter Humphrey
2017-10-23  9:36                 ` Mick [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1876719.iouDLr9l2u@dell_xps \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox