🚀 go-pugleaf

	- hi; in article, <20120727.1344.929633snz@twoplaces.co.uk>,
	   simon@twoplaces.co.uk "Simon Turner" helpfully advised:
>	       colin@cj4386.demon.co.uk "colin may" wrote:
>>I just tried the user and pass, it let me in. Not using telnet very often,
>>I don't know much about the commands to use. Tried list and it showed me,
>>I presume the mail waiting. Any guidance would be welcome.
>
>Thank goodness for that!  I think your best bet for getting hold of your
>new mail is to try my new Large build (v0.3e); I haven't written release
>notes or anything yet, but in brief this has a few tweaks I've made for
>my own devious purposes (most of which aren't present in the standard
>builds) and a bit of minor standardisation work to the SMTP server, plus
>of course the new POP3-SMTP code which grabs messages via POP3 and feeds
>them into the SMTP server, as though they had been sent via SMTP.
>
>The following new builds can by downloaded from my ashes.org.uk web site
>(there's no index page or anything, just files) -- if anyone wants the
>TextWin builds or the PKLite build, let me know:
>
>http://www.ashes.org.uk/gremnos/lrge_03e.zip    Large build

	- not yet looked at; i'll look back to check out what the large
	build allowed me to do, that the lite dropped (iirc, i could
	allow privileged friends to telnet me, and to telnet myself and
	write stuff whilst online - i don't remember aught else now).

>http://www.ashes.org.uk/gremnos/lite_03e.zip    Lite build
>http://www.ashes.org.uk/gremnos/pplt_03e.zip    ppint's custom Lite build

	- downloaded and unzipped, many thanks; not yet investigated,
	which i should probably try to do sometime before i'm forcibly
	migrated - which i'm still dreading); but does your having
	thoughtfully provided me (and potentially others) with a new
	pplite build mean that the ~\demon\mailkill file will have any
	effect upon mail collected by pop3 - or have you kept the pplt
	version because the 03e net.exe retains the ability to accept
	mail by smtp?
>
>The Large build was getting rather big with the new POP3 stuff in there,
>so I removed the old (and I presume long-unused) "rlogin" and "rsh"
>commands[*], which freed up enough space not just for the POP3 stuff,
>but also for the extra dialler logging commands and John Washington's
>HTTP grabber that have hitherto been in all builds apart from Large --
>so there's a bit of extra functionality in the Large build on top of the
>POP3 stuff.

	- i'd completely forgotten john's http grabber command syntax,
	so it was a try-and-retry set of variations before pplt_03e.zip
	was successfully grabbed :-)
>
>Of immediate interest is the new family of "pop3smtp" commands ("pop3"
>for short).  Probably the only one you'll want is "pop3 collect" (unless
>you want to try leaving stuff on the server to begin with in case of
>problems), but I'll describe them all anyway for completeness.  However,
>an executive summary is this:
>
>* If you want to leave messages on the server while doing tests (no
>  messages will be deleted, and they will be downloaded again next time)
>  (default is off), run this:
>    pop3 leave on
>
>* To collect any mail that may have found its way on to the old system,
>  run this (substituting your real hostname and old POP3 password as
>  appropriate):
>    pop3 collect pop3.demon.co.uk host oldpass *env

	- *nods*  could prove useful - but if clueless+witless were
	going to leave the old system up and running for long, they
	could equally well let customers remain on it, couldn't they
	</forlorn devout wish> - ?
>
>* To collect mail from the administrator username on the new system and
>  have it sent to local user "administrator", run this (substituting
>  your real hostname and new POP3 password as appropriate):
>    pop3 collect mail.demon.co.uk administrator@host.demon.co.uk newpass

	- iiuc, it is (will be, for me) possible to re-name the local
	(= on the new system) user, "administrator", to something else,
	and then to create a new user, "administrator", without the
	administrator privileges: i do not yet know whether this will
	divert all the spam sent to non-existent-usernames@i-m-t.dcu
	to this new, unprivileged, "administrator" user on the new
	system - but i hope so, as such junkmail outnumbers legitimate
	mail to i-m-t by between 50 and 100:1.

	- and it does work, i can then leave everything placed by c+w
	on the new, unprivileged "administrator" user's mail on their
	machine until they choose to delete it. (- touch wood.)
>
>* To collect mail from username "fred" on the new system and have it
>  sent to local user "wilma", run this (substituting your real hostname
>  and fred's new POP3 password as appropriate):
>    pop3 collect mail.demon.co.uk fred@host.demon.co.uk fredpass wilma
>
>The details follow.  Note that variable arguments are shown in angle
>brackets <arg> below; the brackets should not be included in the real
>commands!
>
>Please note that you MUST NOT try using the special "*env" fourth
>argument to "pop3 collect" with the new system, unless you want to run
>the risk of mail being deleted unread...
>
>
>pop3 collect <server> <username> <password> [<mailbox>]
>
>        Takes 3 or 4 arguments, as above.
>
>        Connects to <server>, logging in with username <username> and
>        password <password>, and downloads all messages, feeding them in
>        to the SMTP system as though they had been sent to the SMTP
>        server with a recipient name of <mailbox> (if present),
>        otherwise the local-part of <username> if that appears to be an
>        address, or failing that "unknown".

	- i do not, for fairly obvious reason, given the spam:legitimate
	mail ratio, currently have a "default deliver" - or any other
	default line - in my alias file: will this upset pp_03e at all?
>
>        For those who have not been migrated yet, or who want to
>        download from the old system in case anything has ended up
>        there, setting <mailbox> to "*env" tells it to use the old *ENV
>        command (unique to the old SDPS system) to find the real sender
>        and recipient, and also whether the message is new or has
>        already been downloaded.
>
>        DO NOT try using *env with the new system: it doesn't work, and
>        will result in all messages being sent to local-user "*env" with
>        possibly catastrophic consequences ("*" is an illegal character
>        in DOS filenames, which means if *env isn't rewritten to
>        something else first, the recipient will be declared invalid and
>        the message will be rejected, i.e. deleted unread).

	*nod*  thanks for the explicit warning & instruction.
>
>pop3 leave [on | off]
>
>        Sets or reports the current "leave" setting.  If on, leaves
>        copies of messages on the server after collecting them rather
>        than deleting them; with the new platform, it has no way of
>        knowing which messages have already been downloaded, so the
>        messages will be downloaded again next time.  With the old SDPS
>        system and *ENV, messages that have already been read are
>        skipped and not downloaded again.
>
>        Default is off.
>
>
>pop3 bounce [on | off]
>
>        Sets or reports the current "bounce" setting.  If on and a
>        message is rejected on the grounds of sender or recipient
>        (unlikely in the current version), sends a DSN to the address
>        given in the "Return-Path:" header.
>
>        Default is off: leave it that way!

	- i currently (pplt_03d) (unmigrated) reject ~50-98% of mail
	getting through to the smtp queueue on the grounds of sender
	or recipient, using a *lot* of regexps, and every now & then
	adding a new line: i don't particularly want to send dsns to
	most of the apparent senders, but don't know how not to, with
	the current smtp mail delivery system, and amn't sure whether
	the new, post-forced migration, pop3 system will/can use my
	mailkill file at all.  (i'd've guessed not, but am hoping...)
>
>pop3 timeout [<value>]
>
>        Sets or reports the current "timeout" setting.  This is the POP3
>        server response timeout in seconds -- if the server fails to
>        respond to a command within the timeout, aborts the current
>        connection.
>
>        Default is 120 seconds (two minutes); 0 disables timeouts.
>
>
>pop3 trace [<level>]
>
>        Sets or reports the current "trace" level.  With higher levels
>        of tracing, more and more of the POP3 activity (commands and
>        responses etc.) is displayed on the console.
>
>        Default is 0; highest meaningful level is 3.
>     
>
>Hope this helps; let us know how you get on!

	- i'm hoping it does/will, too; i'll do so, as and when...
>
>[*] The "rsh" command never worked anyway: it was unimplemented, and
>just returned 0...

	- i do not recall what it was _meant_ to do - and i've never
	used rlogin, not least because unscheduled & unadvised power
	cuts used to be fairly common here (and still occur a couple
	of times a year), with attendant unpredictable supply spikes.
	leaving i-m-t powered on unattended didn't (and still doesn't)
	seem sensible, despite using an anti-spike spelled socket.

	- and again, thanks for your work;

	- love, ppint. (just been given my hospital date: 21/8/12)
	[drop the "v", and change the "f" to a "g", to email or cc.]
-- 
    "I for one have been eight-bit clean for at least 15 years"
 - keith f. lynch on rec.arts.sf.fandom 20/3/2010 (3/20/2010 for merkins)