dovecot - Apr 2003 - command line version of dovecot?

> From: Kyler Laird <kyler-keyword-dovecot.a0ff9b at lairds.org>
> I finally have dovecot mostly working and I was thinking that
> I'd been saved from having to use UW-IMAPd, but I just now
> noticed that there doesn't appear to be any way to run
> dovecot over standard I/O; it always wants to listen on a
> socket.
There's the "imap" binary that should do exactly that. Usually
installed
into /usr/local/libexec/dovecot/imap

Or did you mean you wanted to run it from inetd? CVS version supports
that too if you execute imap-login.

On Wed, 2003-04-09 at 18:52, Kyler Laird wrote:
> > There's the "imap" binary that should do exactly that.
Usually installed
> > into /usr/local/libexec/dovecot/imap
> 
> Ah!  That's just the kind of solution I sought.
> 
> Unfortunately it doesn't seem to work for me.  It doesn't
> appear (via strace) to read any configuration file.  It just
> looks in /var/mail/[user] for a Maildir.  I need to to go to
> the Maildir in the user's home (and follow other behaviors
> defined in the config file).
It should look into ~/Maildir first, then ~/mail and ~/Mail unless it's
overridden in MAIL environment. You probably have MAIL=/var/mail/user
set, which is why it looks into there.

Currently it doesn't read any configuration file, and I'm not sure if I
should make it do that.. Well, it could be useful but I'd have to figure
out how to prevent unneeded code duplication for config file parsing.
All settings are passed via environment settings, but they're not
documented (they're basically uppercased versions of the setting names
in config file).
> Should I have found all of this in some documentation?  I
> appreciate the help but I feel like I should be reading
> about this on my own somewhere.
doc/mail-storages.txt explains the MAIL environment.