[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: POP3



On Friday 18 December 2015 15:27:08 David Wright wrote:
> On Fri 18 Dec 2015 at 10:32:01 (+0000), Lisi Reisz wrote:
> > On Friday 18 December 2015 09:49:59 Brian wrote:
> > > > > > > > Also, run 'fetchmail --version' for debugging info.
> > >
> > > The guts of my ~/.fetchmailrc are
> > >
> > >   poll     <POP3 server>
> > >   proto    pop3
> > >   user     <Could be bob or bob@example.com>
> > >   password <secret>
> > >   ssl      <May or may not be needed. Depends on the server>
> > >
> > > 'fetchmail -c -v' for testing.
> >
> > Having just by implication been told by someone that only muggles, lusers
> > and/or dinosaurs use POP3, how many others of us will admit to it?  (For
> > the avoidance of doubt, I use POP3.)
> >
> > I won't admit to being a muggle or a luser (who, me?), but I am often
> > prepared to admit to being a dinosaur.  However, in this case I actually
> > don't agree with the premise.  Feel free to tell me that I am deluding
> > myself and that I am indeed a dinosaur in this as well.
> >
> > I just don't, for my use, like a lot of what IMAP does.
>
> Not sure what this has to do with "command not found" and,
> in particular, "command not found [SOLVED]".

It hasn't.  But it is a continuation of the thread and I quoted from a mail in 
the thread.  It does say "was" not "is" in the subject..  But it makes clear 
I am not hijacking, but splitting the thread.  You have removed and not 
quoted the "was".

Lisi
>
> (In fact, I'm not sure how one could possibly _solve_
> "command not found" in the absence of any more context
> in the subject line.)


Reply to: