[prev in list] [next in list] [prev in thread] [next in thread] 

List:       evolution
Subject:    Re: [Evolution] [OT] evolution smtp handling
From:       NotZed <notzed () helixcode ! com>
Date:       2000-05-28 6:30:06
Message-ID: 200005280630.CAA08576 () trna ! helixcode ! com
[Download RAW message or body]

But, any provider could use another one - for example vfolders use
folders from anywhere, and they might also use an mbox as a backing
store ...

So, its not really that more complicated (in so much as the
camel api isn't 'that complicated' to start with anyway).

 Michael

> 
> And a *little* bit more complicated to code given the Camel API
> Because SMTP doesn't know about IMAP which doesn't know about POP or Mbox
> or any other module
> 
> *sigh*
> 
> Why do they have to make these things so complicated? ;-)
> 
> Jeff
> 
> On Sat, 27 May 2000, jm@jmason.org (Justin Mason) wrote:
> > Date: Sat, 27 May 2000 14:50:44 +0100
> > To: fejj@helixcode.com
> > From: jm@jmason.org (Justin Mason)
> > Subject: Re: [Evolution] [OT] evolution smtp handling 
> > 
> > Jeffrey Stedfast said:
> > 
> > > 1. Evolution is not detecting that the smtp server has AUTH (this may
> > or
> > > may not be true, can't tell from the info you pasted)
> > > 
> > > 2. It looks as though at least the MAIL command was completed
> > successfully
> > > which would also suggest that it isn't AUTH (or at least I think so -
> > I'm
> > > not too familiar with the AUTH extension and I don't have the RFC in
> > front
> > > of me)
> > > 
> > > In any event, I need to have more information if I am to solve this
> > > problem. 
> > 
> > BTW, my guess would be that it's requiring POP-before-SMTP, ie. you
> > need to login with POP3 or IMAP first, which adds the username (and/or
> > IP) to a temporary "ok to relay" list.
> > 
> > Obviously not as neat as SMTP AUTH but more widespread at the moment...
> > 
> > --j.
> > 
> > 
> -- 
> Spruce: There are three types of lies: lies, damned lies, and statistics
> 
> 



[prev in list] [next in list] [prev in thread] [next in thread]