🚀 go-pugleaf

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

> On Monday, in article
>      <20120723.1320.929266snz@twoplaces.co.uk>
>      simon@twoplaces.co.uk "Simon Turner" wrote:
> 
> > On Sunday, in article <uSqYShPLqHDQFAnU@highwayman.com>
> >      richard@highwayman.com "Richard Clayton" wrote:
> >
> > > In article <20120721.0929.494snz@cj4386.demon.co.uk>, colin may
> > > <colin@cj4386.demon.co.uk> writes
> > >
> > > >I've received notice of mail migration. Can KA9Q be configured to
> > > >work with this? Any advice will be appreciated.
> > >
> > > if you have a version of KA9Q that can handle POP3 then that can be
> > > configured to work ...
> >
> > From what I've heard on demon.service, the new platform may require
> > STARTTLS encryption for POP3, which would render my POP3-enabled GremNOS
> > unusable without quite a lot of extra work.  I'll find out for sure on
> > Wednesday afternoon, which is when I'm being migrated... 8-(
> >
> 
> Thanks for all the responses. I was supposed to be migrated at 1pm
> today.  How would I know?

I'm not quite sure what question you're asking, so I'll have a bash at
answering two variants.  Sorry this is rather long; I hope one of them
is what you wanted!

Q1. How would I know whether I've been migrated or not?

A1. After migration, all mail will go to the new platform and not to the
    old one.  So, arrange for some mail to be sent to you and see if it
    arrives: if so, you haven't been migrated yet; if not, you have.
    Note that the new platform uses new host names for mail sending
    (SMTP) and collection (OPP3): the old one used post.dcu for sending
    and pop3.dcu for collection; the new one uses smtp.dcu for sending
    and mail.dcu for collection.

    Note that your KA9Q setup may spot the attempt to send mail to
    yourself and deliver it locally instead of going via demon; if you
    like, I can send you a test message instead.  Let me know.

    If you've recently been receiving these lovely virus-laden booking
    confirmation messages, you may already have rather a lot of them
    waiting for you: after only getting 10-20 per day on average for
    several weeks, I seem to have 100+ waiting for me at the moment!  I
    would like to think that the new platform's "improved" antispam
    stuff would block these, but report in demon.service don't sound all
    that encouraging...


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.
    Note that this relies on you being able to type things accurately to
    a live POP3 telnet session (correcting errors with backspace may not
    work as you expect), so only do it if you're reasonably confident
    that you can type things accurately first time.  The test would be
    more useful if there is some mail waiting for you (so do the above
    test first and make sure it doesn't get sent to you by the old
    system, meaning that it should be waiting for you on the new one).

    Your migration mail should tell you the name of the default mailbox
    they have set up for you (administrator@yourhost.demon.co.uk, where
    I presume yourhost will be cj4386) and its password (indicated by
    stars in the sample below).

    Run "telnet mail.demon.co.uk 110" and you should get a dialogue with
    the new POP3 server somewhat like this ("<-" means stuff the server
    sends to you, "->" means stuff you send to it by typing and pressing
    return -- note that the commands I sent were in capitals, e.g. USER
    rather than user, but you can use lowercase if you prefer):

      <- +OK The Microsoft Exchange POP3 service is ready.
      -> USER administrator@********.demon.co.uk
      <- +OK
      -> PASS ********
      <- +OK User successfully logged on.
      -> STAT
      <- +OK 0 0

    If this returns something more like "+OK 5 15354", it means there
    are 5 messages in your mailbox, with combined size 15354 bytes.  If
    so, go on to try some other commands like LIST and TOP as shown
    here:

      -> LIST
      <- +OK 5 15354
      <- [list of message numbers and lengths, one per line]
      <- .
      -> TOP 1 5
      <- 
      <- +OK
      <- [message header]
      <- 
      <- [first 5 lines of message body]
      <- .

    No matter what happens, you should send the QUIT command to end the
    telnet session (in fact, this can be typed at almost any point to
    end the session cleanly if you're not confident about continuing):

      -> QUIT
      <- +OK Microsoft Exchange Server 2010 POP3 server signing off.

    Let us know how you get on; or if you're not sure about doing this
    sort of stuff, and can manage without your mail for a couple of
    days, wait until Wednesday afternoon and I'll run the tests and
    report back to the group.

    As you may have guessed, I was able to have an unencrypted
    conversation with the new server, but I haven't been migrated yet so
    I don't know if that would remain the case after migration.  (I also
    don't know whether connecting via a Demon IP address would make a
    difference; my test was from a non-Demon host.)

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...

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