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

[Alain Magloire]

Bonjour

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

It would be better for you to have cvs writing access.   The procedure
on how to do this  is still a mystery but :
- go to savannah.gnu.org
- create yourself an account
- send me the account name(Please Cc: Jeff)
>From then, I should do something ... not sure what, to give writing access.
Hopefully the Chief Managing Officer(Jeff) will chime in at that point.

Meanwhile, I'll try to find time to commit the cmu-sieve.tar.
Although, I would not enable it yet in the SUBDIRS of the top Makefile,
it is still to hot to handle.

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

I agree, that envelope_t should have a To, envelope_to ();
and default to the header "To:" if none is set.  Making note for the
new implementation and probably update the current this weekend.

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

RFC 2192, IMAP URL Scheme.
http://www.imc.org/rfc2192

> Is there an IMAP url that allows a password?

Nope, they are too much potentials of security risks to allow it.

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

That would be to easy 8-).  No there is no such thing.  However I do not
recall the RFC fixing the syntax of the AUTH field, it is conceivable
to set it to a special keyword that would mean fetch the autenthication
mechanism/info from a file or something.

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

Agreed, it will be nice to have a consistent configuration that even
the other programs pop3d, imap4d could use through the API.
For example something that I did not have time to add in the
IMAP client is login and mailbox referals  meaning you could
redirect some users to other systems or mailbox
"temporairement" temporarely(sp?)
and this could be done transparently, so lets suppose a config file:

## Sam default mailbox
#sam = /var/mail/sam

## Oops! The disk on our host is going bezerk
## fallback.
sam = imap://backup.universe.org

see:
RFC 2193 IMAP4 Mailbox Referrals
RFC 2221 IMAP4 Login Referrals

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

8-), Ok.

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!