Spot on!

The problem was that I (wrongly) assumes that the # character could be used to comment lines in the configuration files. Wrong, of course - and bincimap-up complained, and didn't read the config file to its end.

Also, the logging parameter was set wrong - I set it to multilog but didn't have multilog configured correctly, so I never saw the log output. As soon as I changed log output to "syslog" I actually saw the problems that were occurring. Aargh ;-)

I'll write up a mini-HOWTO on my set-up soon, as promised.

Regards,

- Felix

On 18 Nov 2003, at 19:44, Andreas Aardal Hanssen wrote:

Hi, Felix :-).

On Tue, 18 Nov 2003, felix wrote:
I'm new to bincimap and this mailing list, please excuse me if this is
a dumb question. I read all man pages and articles on the web page
several times, but I am still bit confused regarding our set-up, and
how it can be integrated with bincimap.

If you did and it still didn't work, then there's something we need to improve. :)

I am using vpopmail, but only have one domain. The mailboxes are stored
like this:
/home/vpopmail/domains/domainname.org/felix/Maildir
/home/vpopmail/domains/domainname.org/frank/Maildir
vchkpw will authenticate correctly (this works with bincimap, I've
tested it), and (assuming I'm authenticating as felix) then chdir() to
/home/vpopmail/domain/domainname.org/felix.

Yes; if bincimap-up succeeds in launching bincimapd, then one of the first
things bincimapd does is to change to "path". It does so by passing the
argument of "path" directly to chdir.


One thing that could have happened is that Binc failed to load
bincimap.conf. In this case, the log file should give you a reason. If you
suspect that bincimap.conf is loaded but no log output is generated, a
quick strace with a grep on "open" should give you the answer.


The other is that vchkpw messed up the environment somehow before starting
bincimapd. This you can check by looking up the bincimapd process'
/proc/<pid>/environ file. It should be full of variables like
BINCIMAP_STATE, BINCIMAP_USERID, BINCIMAP_SUBSCRIBED_, BINCIMAP_CONF_,
BINCIMAP_GLOBALCONFIG_ and so on..


(...)
thought that I understood the documentation correctly, and have
configured bincimap as follows:
Mailbox {
    depot = "Maildir++",
    type = "Maildir",
    path = "./Maildir",
    auto create inbox = "yes",
    auto subscribe mailboxes = "INBOX",
    umask = "077"
}
thinking that the parameter "path" would tell bincimap to chdir() into
./Maildir for the incoming mail, and creating its submailboxes in ./
(i.e. in /home/cpopmail/domain/domainname.org/felix) [or will the
folders be created directly within Maildir/?]. One way or the other,
this doesn't work at all. What am I possibly doing wrong? Or am I

They will be created in Maildir/* when all is working correctly. If you want ./ to be used for folders instead, which is perfectly okay, then either "felix" must be a Maildir itself, or you can use IMAPdir and symlink Maildir to INBOX.

I would be very grateful if you could point me in the right direction,
and would volunteer to write something up for the FAQ that would make
it easier for people like me to understand how the pieces fit together
:-)

Sure, please tell us how things go after this.


Andy :-)

--
Andreas Aardal Hanssen   | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP      |  "It is better not to do something
http://www.bincimap.org/ |        than to do it poorly."




Reply via email to