Re: future wishes - ACAP and LDAP support

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Paul Franklin <paul@cs.washington.edu> writes:

> So I might have this in my nnml server definition:
> 
> 	(nnmail-spool-methods
> 		(simple "~/Gnus/outgoing")
> 		(vmpop "pop.cs.washingon.edu:110:pass:paul:*"))

Yes, that's a good idea for a syntax.  Perhaps

(nnmail-spool-methods
 (mbox "~/Gnus/outgoing" :move-function "movemail")
 (pop :server "pop.cs.washingon.edu" :port 110 :password ask :user "paul"
      :protocol apop))

would be clearer, though.  It would be quite extendable, in any case. 

> Then, of course, there's backwards compatibility.  I propose not
> making things strictly backwards compatible, instead making things
> work how novice users probably expect, and forcing expert users to
> possibly do some work.  A server would only use nnmail-spool-file if
> all of these apply for that server:
> 
> * The server is the first mail server in the list of
> 	(cons native-server secondary-servers)
> * nnmail-get-new-mail is t
> * nnmail-spool-file is well-defined
> * nnmail-spool-methods is not defined

Hm.  I think `nnmail-spool-file' should override `nn*-spool-methods'
(or whatever).  So users with more complex needs would set
`nnmail-spool-file' to nil to use the server-specific spool methods.

`nnmail-spool-file' would be extended to support the new syntax,
though.

A related note -- setting server variables is kinda tricky at the
moment, so I think I'll add a setter function for these:

(nnoo-set SERVER VARIABLE VALUE)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen