🚀 go-pugleaf

On Monday, in article
     <20120723.2213.522snz@cj4386.demon.co.uk>
     colin@cj4386.demon.co.uk "colin may" wrote:

> On Monday, in article
>      <20120723.1659.929275snz@twoplaces.co.uk>
>      simon@twoplaces.co.uk "Simon Turner" wrote:
> 
> > Q2. How would I know whether KA9Q-type POP3 collection will work or not?
> >
> > A2. Try a normal text (i.e. unencrypted) POP3 session to the new server.
> >     [...]
> >
> >     Run "telnet mail.demon.co.uk 110" and you should get a dialogue with
> >     the new POP3 server somewhat like this [...]
> >
> > If the new platform will accept plain unenecrypted POP3 for mail
> > collection, I've got a version of GremNOS with POP3 collection
> > integrated in to the SMTP system that may work for you...

> Bit over my head, but I tried the "telnet mail.demon.co.uk 110" it
> came back with the message "pop3 microsoft exchange ready ok" typing
> anyhing after this sends back the message "error protocol 19". I tried
> to email you, no go.  Must have been migrated.

I did eventually receive your mail this morning; your first attempt to
send it probably fell foul of the "greylisting" applied by the people
who host my domain, whereby they initially refuse to accept the mail
with a temporary error, then if you try again after five minutes or so
they will accept it.  (This is an anti-spam measure: spammers often give
up if the first attempt doesn't work, but proper mail systems should
continue to try sending it and eventually get through.)

So at least your outbound sending works; but I doubt you'll see my
reply, because it went to the new platform -- mx1.demon.co.uk -- rather
than punt-*.demon.net as would have been the case before migration.

(Raising the SMTP tracing level will let you see the initial 220
response from the server, which is quite different on the new platform:
"220 smtp.demon.co.uk ESMTP" rather than the old "220
anchor-hub.mail.demon.net ESMTP <date>".)

Disappointing to hear that telnetting to the new POP3 server didn't
work; is there any chance you could try it again, and tell us *exactly*
what it said before you started typing?  And exactly what you typed (if
anything) before it produced the error?  (Obscure hostnames and/or
passwords by all means, but otherwise let us know the precise keys you
pressed.)  Protocol error 19 from MS Exchange seems to mean
"unrecognised command", which suggests it might be some kind of typo
rather than something more fundamental.  (Fingers crossed...)

I can run some tests for myself once I've been migrated tomorrow
afternoon, but the one aspect of your setup I can't reproduce is a
direct connection from a Demon host rather than an external one (I
haven't connected through Demon for years, and don't particularly want
to have to find a modem, an old machine with a serial port etc. just so
I can try it.)

> Version of KA9Q is gremnos v0.3d.

OK, thanks.  Could you tell me the size of the NET.EXE file in bytes, so
I can work out which of the five possible variants you're using?

-- 
Simon Turner                                    DoD #0461
simon@twoplaces.co.uk
    Trust me -- I know what I'm doing!          -- Sledge Hammer