🚀 go-pugleaf

On Friday, in article
     <20120727.1344.929633snz@twoplaces.co.uk>
     simon@twoplaces.co.uk "Simon Turner" wrote:

> On Friday, in article
>      <20120727.0926.2snz@cj4386.demon.co.uk>
>      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
> 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
>
> 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.
>
> 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
>
> * 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
>
> * 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".
>
>         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).
>
>
> 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!
>
>
> 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!
>
>
> [*] The "rsh" command never worked anyway: it was unimplemented, and
> just returned 0...
>

High Simon,

Many thanks for your help. I'll be downloading one of the files and will let
you know how I get on.