bug-mailutils
[Top][All Lists]
Advanced

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

Re: cmu-sieve: starting to work, patch about paths.


From: Sam Roberts
Subject: Re: cmu-sieve: starting to work, patch about paths.
Date: Tue, 29 May 2001 00:43:45 -0400
User-agent: Mutt/1.3.16i

Quoting Alain Magloire <address@hidden>, who wrote:
> How about to commit it in mailutils/sieve, the old template can go, it
> was done in an hour on a rainy day.

Cool by me, tomorrow night I'll rearrange it into a form where you
can add all the files I send you, instead of having to figure out which
should be in, and which are my scratch files. Or do you want to
give me cvs access to the sieve directory?

> >  - The mailer API will need to support submission of a message where
> >    the envelope from and to is NOT parsed out of the message.
> 
> Proposal for the API extension?

I'll get one, and perhaps implement it. That was just so you know
what I'm thinking about.

> And even in .mailpass have a redirection to the ACAP server.  Is there
> an URL std for ACAP? icap://..

I think so.

What's the RFC for IMAP urls? Is there an IMAP url that allows
a password? I would really like to see something like:

  fileinto "imap://sam;AUTH=userpass,address@hidden/l.mailutils"

unless, and perhaps even if, there is a good configuration mechanism.

> > Next on my todo list is tightening up the logging and error reporting,
> > it's a little schizophrenic right now, then I'm going to implement
> > the redirect command. This will require the mailer to send a message
> > to a specified address, not to any of the addresses in to,cc,bcc, and
> > I'll also need to deal with configuration to figure out which mailer
> > to use.
> 
> <Wish>
> If you ever tackle the configuration problem, can you try to make it generic
> so it can be reuse?

Yes, that's why I bring this up. I want to talk about the kind
of information that can be configured, and where to put it into
the API:

- default mailer (smtp, sendmail, procail?, ...)

- default folder (~/Mail, ...)

- default spool file (/var/spool/mail/user, ...)

- default mailbox (~/mbox,...)

- map of URLs to authentication information
   (
     imap://address@hidden passwd=sekrut,
     pop://address@hidden passwd=julie,
     imap://address@hidden  sslkey=~/sslkey.pub,
   ...)

Maybe what's needed is what you suggested, a token_t that
reads auth data from a cfg file, and a mailer_default()
that does something similar, or a maybe a config_t
object, with an ACAP one, and an LDAP one, and....

Ok, it's too late, I'm going to bed to dream of the Grand Unified
Mail Toolkit (or perhaps ma cherie).

Sam


-- 
Sam Roberts <address@hidden> (Vivez sans temps mort!)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]