I'm approaching the maintainer of lifewithqmail.org to include an expanded section for bincimap similiar to the existing qmail-pop3d.
I was hoping to run through my thoughts with the bincimap community to see if this is a sane idea and to reach a concensus on how the install could look.
I've run the idea past Andreas who was very encouraging. I've merged his feedback to date.
I've contacted Dave Sill - author of lifewithqmail to see if he's ok with it. No reply as yet .. fingers crossed ;) I'll also run this past the qmail community once (if) I get Dave's go ahead. I thought I'd bashed it around here first .. the binc community seems a little less intense than the qmail community :)
My goal would be to make bincimap appear to be the natural imap extension for qmail in the same way pop3d is for pop.
-------
Preface so far:
-------
While following the instructions below will leave you with a qmail/pop/imap setup that feels like a coherent whole, bincimap is very much an external product to qmail. Please address binc setup suggestions/comments/questions as relates to the following instructions to myself and general binc queries that can't be satisfied by the available documentation and FAQ to the binc user's mailing list.
-------- Install directories: -------- If the following configure options were used:
./configure --prefix=/var/qmail --sysconfdir=/var/qmail/control
Then binc would be installed side by side with qmail and pop3d.
I'm a bit worried though with security:
... jail path = "/var/qmail/bin", ...
Is it dangerous to give binc access to the qmail executables?
Andreas wrote:
The jail path should just point to somewhere where as little damage as possible can be done. qmail's bin area is perhaps not the best place - the service directory (service/imap etc), however, is a great place. So /var/qmail/control/bincimap/service/imap for instance - perfect.
I forgot! :) .. I had been thinking of manually moving service/imap* to /var/qmail/supervise/ .. is this a bad idea? .. Is there anyway of having configure place them directly into this directory?
This would leave the following directory structure:
/var/qmail/bin/ - the 2 binc executables /var/qmail/man/* /var/qmail/doc/ - the 2 binc docs /var/qmail/control/bincimap.conf and bincimap.pem /var/qmail/supervise/imap and imaps
Is ... jail path = "/var/qmail/supervise/imap", ... still ok?
Alternatively -
./configure --prefix/var/qmail/bincimap --sysconfdir=/var/qmail/bincimap/control ?
I'm using this at the moment and it feels pretty natural ..
Andreas wrote:
It's an idea, it certainly is. :)
:) I do like the idea though of doing ls -l /var/qmail/supervise and seeing imap, imaps, qmail-pop3d, qmail-send, qmail-smtp all hanging out together ..
-------- Services: -------- I did rudely suggest /var/qmail-bincimap ;)
Andreas fairly pointed out:
The qmail prefix strongly implies that binc is a part of
qmail, and that will make binc support questions show up on the qmail
list. That I believe - is not good. :) /service/bincimap or /service/imap is better, IMO.
Any preferences/suggestions? /service/bincimap or /service/imap ?
-------- Logs: -------- Use multilog ..
./configure --localstatedir=/var/log/qmail ??
Andreas wrote:
The qmail rpms use /var/service/qmail/log/main. I'm not quite sure what a qmail user would like there.
lifewithqmail places pop's log under /var/log/qmail/pop3d/ .. I was aiming for /var/log/qmail/bincimap/ and /var/log/qmail/bincimap-ssl. Not sure if localstatedir=/var/log/qmail achieves this? What do experienced qmailer's suggest?
-------- Administration: -------- Provide an update for qmailctl which controls imap and imaps along with qmail and pop3d. Put variables at the top:
POP3="yes" IMAP="no" # don't control IMAP for instance IMAPS="yes"
so the different products can be easily added/removed from control.
-------- Mailbox: -------- In the spirit of binc is not courier, make a clean break and default to IMAPdir
Use bincimap's FAQ example of preserving ~/Maildir as setup by the pop3d. binc uses ~/IMAPdir and links ~/IMAPdir/INBOX to ~/Maildir ?
Andreas wrote:
That's an okay way to do it. Since Maildir is not a mailbox hierarchy, leave Maildir as INBOX and link IMAPdir/INBOX to ~/Maildir/. Or use only IMAPdir/INBOX, and instruct qmail to deliver there, like one of the most recent posts to the binc list had a solution to.
That was me .. I didn't read your FAQ properly :) I was feeling pretty sheepish when I finally came across the above FAQ entry ;) It does have a good clean feel to it though - I'm not sure how the die hard qmailers will feel about having their Maildir relocated? Some options:
* use ~/Maildir and IMAPdir/INBOX linked to ~/Maildir - no changes to qmail * point qmail at ~/Maildir/INBOX - meet qmail half way * point qmail at ~/IMAPdir/INBOX - feels the cleanest solution for me personally
--end--
I apoligise if I'm way out of line and have offended anyone. Do you think this would be a useful thing? Can binc be more naturally integrated with qmail for qmailers?
While trying to ease into qmail/pop/imap lifewithqmail.org very quickly got me up to speed with qmail/pop - the above is what I would have love to had as I tried to ease into imap.
Thanks for your time and feedback!
Andy.
