🚀 go-pugleaf

	- hi; in article, <20120917.1210.932816snz@twoplaces.co.uk>,
	 simon@twoplaces.co.uk "Simon Turner" commented & explained:
>	                   "ppint. at pplay" wrote:
>>	(following article, <20120914.2213.12090153snz@i-m-t.demon.co.uk>,
>>	                      in which i wrote):
>> []
>> >	- since some time between wed sep 12 21:33:35 and thu sep 13
>> >	20:07:59 attempting to collect mail from the original base a/c
>> >	(user, wotsit) has repeatedly failed since 20:08:00 after noting
>> >	that the first two emails (always the same two) are one mailkill
>> >	rejected and one to unknown user address (in the scrolling info
>> >	at the net> and in mail.log).
>
>I didn't comment on this before, but it sounds as though you've still
>got "pop3 leave on" -- we need to get to the bottom of this at some
>stage, as it should be off unless you've explicitly turned it on!

	- i <enter>ed "pop3 leave off" from the net> prompt after the
	first time i dialled up after you commented it should default
	to this state, and haven't knowingly changed matters in this
	regard since: which suggests that the "leave off" doesn't get
	carried out until a normal end to the mail-collecting process
	occurs, as opposed to after each individual email is collected
	(or rejected).  bic(oc)bw :-)
>
>> >	- pop3 'top 2 0 failed: ''
>> >	  close pop3-smtp: 0/5 messages (0 old)
>> >
>> >	- pop3 receive failed: reset/refused
>> >	 [this message comes if i close the dial-up connection without
>> >	  having received a 'top M 0 failed: '' & close pop3-smtp: 0/N
>> >	  messages (0 old) message - i've not included repeats of it] 
>
>The fact that you're getting a "TOP M 0 failed" error means (a) that the
>POP3 collection system isn't in a "receiving data" state -- any data
>from the previous message has (apparently) finished coming in -- and (b)
>that it was a TOP command (which only returns the header, not the body)
>that failed, rather than RETR which is used to grab the whole message.

	- hmmm; "interesting..." - especially as up to 6MB of the email
	in question was collected, the last time i tried seeing what
	happened if i just stayed online, in the wee smal hours - and
	had to delete a lock file on the mailbox it was headed for, or
	at least chose to, after i eventually gave up and disconnected.

>>	- a couple of overnight dial-up connections on, i'm no longer
>>	so certain; staying online whilst doing nothing but the occas-
>>	ional "asystat<enter>"/"as<enter>" showed that *something* was
>>	still incoming, every now & then, until the connection dropped.
>
>You can find out whether the POP3-SMTP socket is still receiving data by
>looking up its socket number ("socket"), then running "socket NNN" a
>couple of times and comparing the rcvd totals.

	- ah; yes, i should've thought of that - i've only ever previously
	checked ftp, hop check, ping and similar sessions.
>
>It still looks to me as though something is going wrong, rather than the
>whole thing running normally but taking ages to be received a large
>message.

	- ok; *bows* to greater experience & knowledge of such things :-)
	  (or possibly - but hopefully not - s/rather than/as well as/.)
[]
>The GremNOS POP3 collection picks them up in message order (1, 2, ...),
>which seems to be the order in which the messages arrived in the mailbox;
>size of message doesn't come into it.  (Although it could: see below.)

>>	- cos if not, and someone (or something) sends a ginormous mail
>>	to a live mailbox your domain, then it'll jam things up good'n'
>>	proper, won't it?
>
>Yup, it will.  I hadn't given enough thought to that (having a nice fast
>FTTC connection rather than dialup). 8-(

	- s/8-(/8-0/ ?      - [a]
[>>]
>
>Two improvements spring to mind: (a) modify the POP3 collection to allow
>GremNOS to collect the messages in ascending size order rather than in
>message number order; (b) implement Pete's ESMTP SIZE restrictions for
>POP3 as well, which would allow you to set a size threshold above which
>messages wouldn't be downloaded.

	- will the latter reject messages above the threshold, or leave
	them uncollected?  if the latter, this might trigger the strange
	behaviour seen above, where messages rejected as killfiled/to an
	unknown user-name are actually left on, despite "pop3 leave off"
	being the most recent instruction.      - [b]

[snip A quick POP3 lesson and examples - for both of which, many thanks]
[saved for further study & future reference :-)]

>If you wish to record the session to a file, press F10 to get back to
>the prompt, enter "record pop3.rec" (to record to file POP3.REC) then
>press Enter to return to the session.  Recording will stop when the
>session closes, or when you enter "record off" at the net> prompt.

	- *nods* - except i'll need to remove any & all finger (etc.)
	lines from my autoexec.net when i wish to record pop3 sessions,
	as something doesn't re-set when an smtp session ends - nor,
	when an ftp session ends (which it used to, sort of - formerly,
	it'd re-set to another (the next-highest numbered, iirc) session.
	[or is it properly "socket"?], if any were still live, when
	"<enter>" was typed from net>). (- [c])   - o.k.

	- ?  or possibly, type "s<enter>" to find which "s<0-9><enter>"
	to type to get to the pop3 session - ? (note to self: try it.)

	- love, ppint.

	[a] - may require interpolation of the odd "\"

	[b] - a reasonable response to which might be, "we;ll burn that
	      bridge when we come to it"

	[c] - separate point, & 'ware newsthread crossing with emails

	[drop the "v", and change the "f" to a "g", to email or cc.]
-- 
       "The Wikipediasts want to believe that they're working on an
    important project to collect and organize the knowledge of the ages,
  and it offends them if it doesn't (yet) include a detailed history of the
 Napoleonic Wars but does include a complete episode guide to Danger Mouse."
   - Mike Schilling on rasfwr,ff 17:37 GMT 14/6/07 (6/14/07 for merkins)